I know that GitHub Action manual triggers is a very discussed issue, manual approval is a bit less discussed but still present in the community.
I have a question for those who use Github actions for CD purposes.
As you know Bitbucket, Gitlab, Azure Devops etc. have a feature Manual approval which means that a pipeline can reach a certain step in the process for example: build -> test -> deploy to staging.
The next step is deploy to production yet it needs a manual approval or trigger. So my question is this, were any of you achieve that functionality in GitHub action with the same information (branch name, same test results) without running the whole pipeline again? (It's kind of the reason why I am not migrating us from Bitbucket to GitHub yet)
Thank you for your answers
Recently, the GitHub team has announced Environments in beta. With this feature, you can add Manual approvals into your CI/CD.
However, there is a restriction for private repositories - Only GitHub Enterprise service plan can use Environments within private repositories.