-
Notifications
You must be signed in to change notification settings - Fork 66
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
ci: add workflow for the Bounty Program commands #277
ci: add workflow for the Bounty Program commands #277
Conversation
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.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
with: | ||
github-token: ${{ secrets.GH_TOKEN }} | ||
script: | | ||
const commentText = `❌ @${{github.actor}} is not authorized to use a Bounty Program's command.`; |
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.
maybe we should mention you and Thulie in comment
- so it is clear who is authorized
- so you are automatically pinged and see that people want to use it
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.
lgtm, please add it to https://github.com/asyncapi/.github/blob/master/.github/workflows/global-replicator.yml#L130 as this is a workflow that must end up in every repository.
and yeah, please when you add a change, do not do force push, it is not helping in review 😅
|
/rtm |
This PR adds GitHub Actions workflow to allow Bounty Team members to issue commands to the organization's global AsyncAPI bot related to the Bounty Program, while at the same time preventing unauthorized users from misusing them.
This particular workflow adds a command that allows adding the label
bounty
to GitHub issues, thereby making them Bounty Issues.Command is invoked on creation of comment
/bounty
.