Skip to content

Add Github action to close stale issues #2981

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

Merged
merged 2 commits into from
Apr 18, 2025
Merged

Add Github action to close stale issues #2981

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2bf8dec
Add Github action to close stale issues
AmirhosseinPoolad Apr 15, 2025
41427ae
Add documentation for automatic issue closure
AmirhosseinPoolad Apr 17, 2025
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
31 changes: 31 additions & 0 deletions .github/workflows/stale.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
name: 'Close Stale Issues'
on:
schedule:
# Run everyday at 1 PM UTC
- cron: '0 13 * * *'

jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
with:
# The message to be shown for stale issues
stale-issue-message: 'This issue has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you believe this is still an issue, please add a comment.'
close-issue-message: 'This issue has been marked stale for 15 days and has been automatically closed.'
# If you want to exempt an issue from being marked stale/deleted, label it as 'no-stale'
exempt-issue-labels: 'no-stale'
days-before-issue-stale: 365
days-before-issue-close: 15
# Start from the oldest issues
ascending: true

# The configuration below can be used to allow the same behaviour with PRs.
# Since we currently don't want to close old PRs, it is commented out but
# left here in case we change our mind.

# stale-pr-message: 'This PR has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you are still working on this PR, please add a comment.'
# close-pr-message: 'This PR has been marked stale for 15 days and has been automatically closed.'
# exempt-pr-labels: 'no-stale'
# days-before-pr-stale: 365
# days-before-pr-close: 15
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ This information helps us to quickly reproduce (and hopefully fix) the issue:

Tell us what version of VTR you are using (e.g. the output of `vpr --version`), which Operating System and compiler you are using, or any other relevant information about where or how you are building/running VTR.

Once you've gathered all the information [open an Issue](https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/new?template=bug_report.md) on our issue tracker.
Once you've gathered all the information [open an Issue](https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/new?template=bug_report.md) on our issue tracker. Issues that do not have any activity for a year will be automatically marked as stale and will be closed after 15 days of being marked as stale.

If you know how to fix the issue, or already have it coded-up, please also consider [submitting the fix](#submitting-code-to-vtr).
This is likely the fastest way to get bugs fixed!
Expand Down