GitHub action Manual approval process

Question

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

Nation

Answer 1

Recently, the GitHub team has announced Environments in beta. With this feature, you can add Manual approvals into your CI/CD.

Environment workflow syntax

However, there is a restriction for private repositories - Only GitHub Enterprise service plan can use Environments within private repositories.

Tita

Is there a way to use manual approval without deployments? I'd like to have an authorized user choose whether to sign an RPM on my stable branch or not – Popinjay

According to this doc, "Organizations with GitHub Team and users with GitHub Pro can configure environments for private repositories." – Swee

oh but this doc says, "If you are on a GitHub Free, GitHub Pro, or GitHub Team plan, required reviewers are only available for public repositories." – Swee

Answer 2

So in GitHub there are two ways to do manual approval for deployments .

1. Using Environments
2. Using GitHub action

Irreparable

As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center. – Peipus