You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.'
15
+
close-issue-message: 'This issue has been marked stale for 15 days and has been automatically closed.'
16
+
# If you want to exempt an issue from being marked stale/deleted, label it as 'no-stale'
17
+
exempt-issue-labels: 'no-stale'
18
+
days-before-issue-stale: 365
19
+
days-before-issue-close: 15
20
+
# Start from the oldest issues
21
+
ascending: true
22
+
23
+
# The configuration below can be used to allow the same behaviour with PRs.
24
+
# Since we currently don't want to close old PRs, it is commented out but
25
+
# left here in case we change our mind.
26
+
27
+
# 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.'
28
+
# close-pr-message: 'This PR has been marked stale for 15 days and has been automatically closed.'
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ This information helps us to quickly reproduce (and hopefully fix) the issue:
77
77
78
78
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.
79
79
80
-
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.
80
+
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.
81
81
82
82
If you know how to fix the issue, or already have it coded-up, please also consider [submitting the fix](#submitting-code-to-vtr).
0 commit comments