-
Notifications
You must be signed in to change notification settings - Fork 103
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
Added GitHub action to auto-merge #55
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bkontur
reviewed
Oct 3, 2023
Added two GitHub actions to enable auto-merge in the repository. This resolves polkadot-fellows#41 ## [Auto-Merge-Bot](https://github.com/paritytech/auto-merge-bot) This bot allows _public_ members of the organization and the author of the PR to enable/disable auto-merge in a PR. It also has a field for a list of users who are also allowed to trigger the bot. For that we have the second action.
## [Get Fellows Action](https://github.com/paritytech/get-fellows-action) This action gets the fellows from the chain data and it extracts their GitHub handles. This handles are then input into the `auto-merge-bot` action as a list of users who are allowed to trigger the bot.
I have also updated the Pull Request template to mention the existence of this bot to new contributors.
Closed
mordamax
approved these changes
Oct 3, 2023
@Bullrich could you please update the |
Updated the readme to contain information about the bot, how to use it, and a link to its documentation
Bullrich
commented
Oct 3, 2023
|
||
This will enable [`auto-merge`](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request) in the Pull Request (or merge it if it is ready to merge). | ||
|
||
The automation can be triggered by the author of the PR or any fellow whose GitHub handle is part of their identity. |
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.
bkchr
approved these changes
Oct 5, 2023
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.
Ty!
xlc
approved these changes
Oct 9, 2023
shawntabrizi
approved these changes
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added two GitHub actions to enable auto-merge in the repository.
This resolves #41
Auto-Merge-Bot
This bot allows public members of the organization and the author of the PR to enable/disable auto-merge in a PR. It also has a field for a list of users who are also allowed to trigger the bot. For that we have the second action.
Get Fellows Action
This action gets the fellows from the chain data and it extracts their GitHub handles. This handles are then input into the
auto-merge-bot
action as a list of users who are allowed to trigger the bot.I have also updated the Pull Request template to mention the existence of this bot to new contributors.