-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
create-issue: add action #588
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Sean Molenaar <SMillerDev@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I think it might be nice to make this a little higher level such that it will also autoclose an issue on success and open a new issue on failure. Maybe even post more comments on repeated failures? Thoughts?
required: false | ||
default: ${{ github.token }} | ||
repository: | ||
description: Repository to send the issue to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: Repository to send the issue to | |
description: Repository to create the issue in |
Sorry, have been a little bit busy this week. I'll get back to this soon.
How about this: we turn this into an action that's able to perform the following depending on
With usage like: - uses: Homebrew/actions/create-issue@master
with:
token: ${{ github.token }}
repository: ${{ github.repository }}
update-existing: true
close-existing: true
dependent-step-conclusion: ${{ steps.deploy.conclusion }}
title: Deployment failed
body: Issue body (or comment to post if issue already exists)
labels: label1,label2
assignees: user1,user2 |
Related: Homebrew/homebrew-core#190657 (comment)