Close stale issues #1229
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: 'Close stale issues' | |
| on: | |
| schedule: | |
| - cron: '0 8 * * *' | |
| jobs: | |
| stale: | |
| if: github.repository == 'glpi-project/glpi' | |
| permissions: | |
| issues: write # for actions/stale to close stale issues | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/stale@v9 | |
| with: | |
| stale-issue-message: >- | |
| There has been no activity on this issue for some time and therefore it is considered stale | |
| and will be closed automatically in 10 days. | |
| If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, | |
| feel free to add a comment to revive this issue. | |
| If it is related to a new feature, please open a topic to discuss with community about this enhancement | |
| on [suggestion website](https://glpi.userecho.com/). | |
| You may also consider taking a [subscription](https://glpi-project.org/subscriptions/) to get professionnal | |
| support or [contact GLPI editor team](https://portal.glpi-network.com/contact-us) directly. | |
| days-before-issue-stale: 60 | |
| days-before-pr-stale: -1 # PR will be marked as stale manually. | |
| days-before-close: 10 | |
| exempt-issue-labels: "bug,enhancement,question,security" # Issues with "bug", "enhancement", "question" or "security" labels will not be marked as stale | |
| exempt-all-milestones: true # Do not check issues/PR with defined milestone. | |
| ascending: true # First check older issues/PR. | |
| operations-per-run: 750 # Max API calls per run. |