---
title: "Comment by Corey Seliger on \"Why You Should Not Use The Version Tag Or Branch Name When Using GitHub Actions\" | Hashnode"
description: "The security concern makes sense. However, why not fork the action and have complete control, refreshing from upstream at your leisure and comfort? What if the"
url: "https://hashnode.com/posts/why-you-should-not-use-the-version-tag-or-branch-name-when-using-github-actions/6031479c72a689446db3e025/comment/6292503b0989e6b52feafcb6"
---

[Discussion](https://hashnode.com/posts/why-you-should-not-use-the-version-tag-or-branch-name-when-using-github-actions/6031479c72a689446db3e025)

Comment [Why You Should Not Use The Version Tag Or Branch Name When Using GitHub Actions](https://hashnode.com/posts/why-you-should-not-use-the-version-tag-or-branch-name-when-using-github-actions/6031479c72a689446db3e025)

[Corey Seliger](https://hashnode.com/@seliger)

[May 28, 2022](https://hashnode.com/posts/why-you-should-not-use-the-version-tag-or-branch-name-when-using-github-actions/6031479c72a689446db3e025/comment/6292503b0989e6b52feafcb6)

The security concern makes sense. However, why not fork the action and have complete control, refreshing from upstream at your leisure and comfort? What if the author decided to no longer host that code?
