THIS IS A TEST INSTANCE ONLY! REPOSITORIES CAN BE DELETED AT ANY TIME!

This is Gitea test Portainer repository mirror from Github
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

55 lines
1.8 KiB

  1. # Config for Stalebot, limited to only `issues`
  2. only: issues
  3. # Issues config
  4. issues:
  5. daysUntilStale: 60
  6. daysUntilClose: 7
  7. # Limit the number of actions per hour, from 1-30. Default is 30
  8. limitPerRun: 30
  9. # Issues with these labels will never be considered stale
  10. exemptLabels:
  11. - kind/enhancement
  12. - kind/feature
  13. - kind/question
  14. - kind/style
  15. - kind/workaround
  16. - bug/need-confirmation
  17. - bug/confirmed
  18. - status/discuss
  19. # Only issues with all of these labels are checked if stale. Defaults to `[]` (disabled)
  20. onlyLabels: []
  21. # Set to true to ignore issues in a project (defaults to false)
  22. exemptProjects: true
  23. # Set to true to ignore issues in a milestone (defaults to false)
  24. exemptMilestones: true
  25. # Set to true to ignore issues with an assignee (defaults to false)
  26. exemptAssignees: true
  27. # Label to use when marking an issue as stale
  28. staleLabel: status/stale
  29. # Comment to post when marking an issue as stale. Set to `false` to disable
  30. markComment: >
  31. This issue has been marked as stale as it has not had recent activity,
  32. it will be closed if no further activity occurs in the next 7 days.
  33. If you believe that it has been incorrectly labelled as stale,
  34. leave a comment and the label will be removed.
  35. # Comment to post when removing the stale label.
  36. # unmarkComment: >
  37. # Your comment here.
  38. # Comment to post when closing a stale issue. Set to `false` to disable
  39. closeComment: >
  40. Since no further activity has appeared on this issue it will be closed.
  41. If you believe that it has been incorrectly closed, leave a comment
  42. and mention @itsconquest. One of our staff will then review the issue.
  43. Note - If it is an old bug report, make sure that it is reproduceable in the
  44. latest version of Portainer as it may have already been fixed.