-
Notifications
You must be signed in to change notification settings - Fork 471
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 stale issue and PR labeler workflows #2485
Add stale issue and PR labeler workflows #2485
Conversation
8a93eef
to
3984e3d
Compare
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.
Some suggestions, can you also squash commits please? Thanks
Signed-off-by: Shaun Thompson <shaun.thompson@docker.com>
15ab468
to
d82e050
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
325f10b
to
9d2e9df
Compare
Pushed extra commits for stale workflow. First one to prefix labels with Move permissions to job similar to And last one related to #2485 (comment) so we can manually trigger the workflow to check its behavior. Tested in: |
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
PTAL @tonistiigi @thaJeztah as I pushed extra commits 🙏
I'm going to break apart this submission into multiple parts to help isolate changes that might need more discussion.
|
This PR adds Close Stale Issues and PR Labeler action workflows. Durations for stale item comments and closure are initial suggestions.
A first attempt was made in a previous PR that had great comments (thanks @crazy-max and @thaJeztah). This iteration drops the 3rd-party auto-labeler and strictly focuses on official GitHub actions.
Goals
Close Stale Issues
General
The configuration as proposed will exempt Issues and PRs that have been assigned milestones (even arbitrarily long ones such
v-future
). In addition, the workflow would process only items created after thestart-date
. We can adjust this date as desired. There is also an option to exempt items that have been assigned to a user.Issues
Notable configuration options
Pull Requests
Notable configuration options
Pull Request Labeler
At present, this is primarily applying
area/*
labels but can be extended if it helps.