OPEN-37 Add new command, schedule and PR functionality #1
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.
Description
This PR implements the following state machine triggered by:
Commands to the bot
“@any assign me”: works only for “New” issues, changes status to “In progress”, assignes @any-association to the issue, saves comment’s author name to “Lead contributor”
“@any unassign me”: works only for “In progress” issues, changes status to “New”, removes assignee, removes the content of “Lead contributor”
Timer, works only for “In progress” issues
on the 6th day of inactivity in the issue posts a comment with the message “@{lead-contributor}, please confirm that you’re still working on this by commenting this issue”
on the 7th day of inactivity in the issues posts a comment with the message “@{lead-contributor}, the issue is now available for other contributors due to inactivity”, changes status to “New”, removes assignee, removes the content of “Lead contributor”
Events related to PRs
works only for “In progress” issues, if PR is linked, then changes status to “In review”
works only for “In review” issues, if PR is unlinked, then changes status to “In progress”
works only for “In review” issues, if PR is closed without merging, then changes status to “In progress”
works only for “In review” issues, if PR is merged, then changes status to “Done”
What type of PR is this? (check all applicable)
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?