Skip to content
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.

Sign up for GitHub

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

[SAME VERSION] Workflow to mark inactive issues/PRs as stale and eventually close them #363

Merged
merged 6 commits into from
Aug 26, 2021
Merged

[SAME VERSION] Workflow to mark inactive issues/PRs as stale and eventually close them #363

Changes from 4 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
974a70b
add stale issues marker workflow
romoh Aug 19, 2021
9d490f8
update based on feedback
romoh Aug 23, 2021
e1ec972
update
romoh Aug 23, 2021
fa07ff3
not
romoh Aug 23, 2021
23aebfb
update messages
romoh Aug 24, 2021
1972435
dry-run
romoh Aug 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .github/workflows/stale-tasks.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# This is a workflow that runs periodically to mark issues/prs with no recent activity as stale, it also closes/removes label based on following activity

name: Mark and close stale issues/PRs
on:
schedule:
- cron: '0 0 * * *' # runs daily at 12:00 am UTC

jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v4
with:
stale-issue-label: stale
stale-pr-label: stale
days-before-stale: 45
days-before-close: 45
remove-stale-when-updated: true
stale-issue-message: >
Issue has been automatically marked as stale because it has been open for 45 days with no activity. Issue will be closed if no further activity occurs.
Thank you for your contributions.
stale-pr-message: >
PR has been automatically marked as stale because it has been open for 45 days with no activity. PR will be closed if no further activity occurs.
Thank you for your contributions.
exempt-issue-labels: keep-alive
token: ${{ secrets.GITHUB_TOKEN }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to double check ... does {secrets.GHTOKEN} have any issue with PRs from forks?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't be a problem. The token should have enough permissions to add labels, add comments and close PR.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my curiousity was more around whether a forked pr would have access to secrets. i think it is ok, but wanted to make sure we tried it.