I would like to remove “actions” tab on my github private repository as well as restrict users from clicking on " Run workflow " on my environment ( QA ) inside my private repository.
I would like to know how to review and approve “Run workflow” in an environment ( QA ) inside my private repository.
Please help how this can be achieved in github actions.
Hi, to disable Actions on a specific repository, on the Settings tab of this repository, navigate to Actions , select Disable Actions for this repository. This will remove the Actions tab but also completely disable the feature, so you won;t be able to run any workflow anymore... unfortunately it is not possible to keep Actions enabled but remove the tab.
About the approval, if you are in GitHub Enterprise you can use the GitHub Actions Environment features, which includes approvals (take a look at it here: youtu.be/w_37LDOy4sI)
If, instead, you are not in GitHub Enterprise, you need to find a workaround for that... one possible solution is using the IssueOps approach as I describe step-by-step in this video: youtu.be/MDOn9HAS7bQ
I would like to remove “actions” tab on my github private repository as well as restrict users from clicking on " Run workflow " on my environment ( QA ) inside my private repository.
I would like to know how to review and approve “Run workflow” in an environment ( QA ) inside my private repository.
Please help how this can be achieved in github actions.
Hi, to disable Actions on a specific repository, on the Settings tab of this repository, navigate to Actions , select Disable Actions for this repository. This will remove the Actions tab but also completely disable the feature, so you won;t be able to run any workflow anymore... unfortunately it is not possible to keep Actions enabled but remove the tab.
About the approval, if you are in GitHub Enterprise you can use the GitHub Actions Environment features, which includes approvals (take a look at it here: youtu.be/w_37LDOy4sI)
If, instead, you are not in GitHub Enterprise, you need to find a workaround for that... one possible solution is using the IssueOps approach as I describe step-by-step in this video: youtu.be/MDOn9HAS7bQ
Thank you Dave,