starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add GitHub Stale bot for issue management #2951

New Issue
Closed
opened 2025-12-29 18:23:58 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:23:58 +01:00
Owner
Copy Link

Originally created by @lampwins on GitHub (Oct 13, 2019).

Proposed Changes

The core maintainers have discussed and decided to try out the GitHub Stale bot to assist in managing the flow of incoming issues. Stale bot will be added to the org and enabled on the netbox repo. To start with, issues will be marked as stale after 14 days of no activity. Then after 7 more days of inactivity, the issue will be closed. Any issue with either the "status: accepted" or "status: gathering feeback" labels applied will be exempt from all Stale bot actions.

This policy will be published in our CONTRIBUTING guide and is subject to change over time.

Justification

The flow of incoming issues to netbox has greatly increased in recent months. Given this added strain on the maintainers, it is natural that some new issues get more attention than others. Often this is a metric of an issues's overall usefulness to the project. In other cases in which issues mearly get lost in the shuffle, notifications from Stale bot can bring renewed attention to potentially meaningful issues.

Stale bot will be used as a tool to help the maintainers keep up with and groom the ever-growing backlog of work.

Originally created by @lampwins on GitHub (Oct 13, 2019). <!-- NOTE: This type of issue should be opened only by those reasonably familiar with NetBox's code base and interested in contributing to its development. Describe the proposed change(s) in detail. --> ### Proposed Changes The core maintainers have discussed and decided to try out the GitHub Stale bot to assist in managing the flow of incoming issues. Stale bot will be added to the org and enabled on the netbox repo. To start with, issues will be marked as stale after 14 days of no activity. Then after 7 more days of inactivity, the issue will be closed. Any issue with either the "status: accepted" or "status: gathering feeback" labels applied will be exempt from all Stale bot actions. This policy will be published in our [CONTRIBUTING guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md) and is subject to change over time. <!-- Provide justification for the proposed change(s). --> ### Justification The flow of incoming issues to netbox has greatly increased in recent months. Given this added strain on the maintainers, it is natural that some new issues get more attention than others. Often this is a metric of an issues's overall usefulness to the project. In other cases in which issues mearly get lost in the shuffle, notifications from Stale bot can bring renewed attention to potentially meaningful issues. Stale bot will be used as a tool to help the maintainers keep up with and groom the ever-growing backlog of work.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 18:23:58 +01:00
adam closed this issue 2025-12-29 18:23:58 +01:00
adam commented 2025-12-29 18:23:59 +01:00
Author
Owner
Copy Link

@Grokzen commented on GitHub (Oct 13, 2019):

@lampwins Three questions. Is 21 days short for issues to be atomatically closed? Some of the issues on the main-page would be closed with these esttings. Two, will you maintainers do a pass on all current open issues to check them for the 2 labels that will stop it from being stale? I have found plenty of them from the past that is either blocked or have only UI as label. Three, consider adding Blocked as a option to be excluded from the bot? There is some issues on older pages that had this case and they would then be stale with these settings.

@Grokzen commented on GitHub (Oct 13, 2019): @lampwins Three questions. Is 21 days short for issues to be atomatically closed? Some of the issues on the main-page would be closed with these esttings. Two, will you maintainers do a pass on all current open issues to check them for the 2 labels that will stop it from being stale? I have found plenty of them from the past that is either blocked or have only UI as label. Three, consider adding `Blocked` as a option to be excluded from the bot? There is some issues on older pages that had this case and they would then be stale with these settings.
adam commented 2025-12-29 18:23:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 17, 2019):

Is 21 days short for issues to be atomatically closed?

Honestly, no. If no one responds to the issue in three weeks either no one feels it needs to be addressed or we're all dead.

Two, will you maintainers do a pass on all current open issues to check them for the 2 labels that will stop it from being stale?

Yes; I just completed a good amount of cleanup prior to merging @lampwins' PR.

Three, consider adding Blocked as a option to be excluded from the bot?

Done.

There is likely to be some trial and error involved as we learn what workflow makes the most sense with regard to stalebot. Rest assured that the maintainers team will adapt the policy as necessary.

@jeremystretch commented on GitHub (Oct 17, 2019): > Is 21 days short for issues to be atomatically closed? Honestly, no. If no one responds to the issue in three weeks either no one feels it needs to be addressed or we're all dead. > Two, will you maintainers do a pass on all current open issues to check them for the 2 labels that will stop it from being stale? Yes; I just completed a good amount of cleanup prior to merging @lampwins' PR. > Three, consider adding Blocked as a option to be excluded from the bot? Done. There is likely to be some trial and error involved as we learn what workflow makes the most sense with regard to stalebot. Rest assured that the maintainers team will adapt the policy as necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: housekeeping
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2951
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?