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 a recurring GitHub job to clean up issues which need revisions #9639

New Issue
Closed
opened 2025-12-29 21:20:09 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:20:09 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (May 9, 2024).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

Employ the close-stale-issues GitHub action to automatically remind posters about issues that need further revision, and close out those that have not received any follow-up response. This can be implemented by largely copying the current workflow for stale issues and adjusting the timers & messaging appropriately. My proposed timers are below, but these are up for debate.

  • After one week has passed with no updates, post a reminder message that additional information is needed for the issue to progress.
  • If no further information has been provided after two weeks, automatically close the issue. (If the author returns in the near future and provides the requested details, the issue can be reopened.)

Justification

Our current issue triage policy contains several paths that end with applying the revisions needed status label to an issue, but does not specify any mechanism for ensuring that those issues are revisited. I try to review these issues occasionally but they often turn stale. Introducing the automated workflow described above will remind people who have submitted issues that need further attention, and automatically close issues which have been abandoned.

Originally created by @jeremystretch on GitHub (May 9, 2024). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes Employ the [close-stale-issues](https://github.com/marketplace/actions/close-stale-issues) GitHub action to automatically remind posters about issues that need further revision, and close out those that have not received any follow-up response. This can be implemented by largely copying the current workflow for [stale issues](https://github.com/netbox-community/netbox/blob/develop/.github/workflows/close-stale-issues.yml) and adjusting the timers & messaging appropriately. My proposed timers are below, but these are up for debate. * After one week has passed with no updates, post a reminder message that additional information is needed for the issue to progress. * If no further information has been provided after two weeks, automatically close the issue. (If the author returns in the near future and provides the requested details, the issue can be reopened.) ### Justification Our current [issue triage policy](https://github.com/netbox-community/netbox/wiki/Issue-Intake-Policy) contains several paths that end with applying the [revisions needed](https://github.com/netbox-community/netbox/issues?q=is%3Aissue+is%3Aopen+label%3A%22status%3A+revisions+needed%22) status label to an issue, but does not specify any mechanism for ensuring that those issues are revisited. I try to review these issues occasionally but they often turn stale. Introducing the automated workflow described above will remind people who have submitted issues that need further attention, and automatically close issues which have been abandoned.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 21:20:09 +01:00
adam closed this issue 2025-12-29 21:20:10 +01:00
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#9639
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?