Automatic Merge In Timeout

[0x4007]

Overview

• We need to maintain a bias of always moving forward in Ubiquity.
• This plugin can be considered dangerous if not configured properly, but the general idea is that if reviewers forget about a pull, it should automatically be merged in after a timeout period.
• The clock is based on the last timeline activity event on that particular pull request.
• This must be eligible to generate payment permits.

Default configs:

1. Collaborator Minimum Approvals Required: 0
2. Contributor Minimum Approvals Required: 1
3. Collaborator Merge Timeout (Days): 3.5
4. Contributor Merge Timeout (Days): 7[^1^]

Remarks

• Worst case scenario, the pull can be reverted. If a pull is detected to be reverted, perhaps a stretch goal of this plugin would be to disable automatic merges again for pulls associated to the same task.
• This would be a wildcard event plugin.

[^1^]: Negative numbers can represent disabled i.e. -1

[0x4007]

I assume it'll take a week in total including to also write unit tests etc.