-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ApproveOps: GitHub IssueOps with Approvals | josh-ops #14
Comments
interesting approach - I have created similar one using graphql and adding dependency on subsequent jobs... So in my case approval will only start when a specific comment exxcluding my account would be triggered :)
|
@RafPe That's a great example of a complex condition!
And I see, so not so much of an approval per se, but requiring someone other than the pull request creator to issue the command. , Also, setting the job as "failed" if it doesn't meet the requirements. I go back and forth, but I don't like my job showing as "red" (aka failed) if it is missing something like this since then it kind of looks like something went wrong. In my favorite example of this, I just don't run the second job when it doesn't meet the criteria. |
ApproveOps: GitHub IssueOps with Approvals | josh-ops
Using GitHub Actions to build automation on top of Issues (IssueOps) with Approvals from someone in a designated GitHub team
https://josh-ops.com/posts/github-approveops/
The text was updated successfully, but these errors were encountered: