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
Add pull request prune functionality #247
Conversation
|
@rwestberg This change can now be integrated. The commit message will be:
Since the source branch of this PR was last updated there have been 2 commits pushed to the Since there are no conflicts, your changes will automatically be rebased on top of the above commits when integrating. If you prefer to do this manually, please merge
|
Webrevs
|
What is the motivation for doing this? I'm not sure that I would find this a useful behavior. |
This will allow stale pull requests to eventually be closed, without manual intervention. The duration can be configured per project (or not enabled at all), as different projects may have different needs. |
After discussing this a bit with Kevin offline, I've updated the logic to send an initial notice before proceeding with the actual close. |
@edvbld Please have another look! |
@kevinrushforth Thanks for reviewing! |
/integrate |
@rwestberg The following commits have been pushed to master since your change was applied: Your commit was automatically rebased without conflicts. Pushed as commit e75c0b0. |
Mailing list message from Robin Westberg on skara-dev: Changeset: e75c0b0 Add pull request prune functionality Reviewed-by: ehelin, kcr
|
Hi all,
Please review this change that adds another mode to the bridgekeeper bot that closes PRs after a configurable period of inactivity.
Best regards,
Robin
Progress
Approvers