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

Run periodic GitHub actions on upstream repository only #10773

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

Originally created by @alehaa on GitHub (Feb 16, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.2.3

Feature type

Change to existing functionality

Proposed functionality

The official NetBox repository contains actions to perform certain tasks periodically, such as updating the translations. I suggest restricting these periodic actions to using the official repository only:

if: github.repository == ‘netbox-community/netbox’

An alternative might be to check if the required authentication tokens are available for those cronjob actions, so that forks can still use those actions.

Use case

Actions should be enabled in forks to run test cases. While this is beneficial, periodic actions often send emails, e.g. about missing tokens. Restricting these actions to NetBox upstream would concentrate the actions where they are needed and avoid error messages in forks.

Database changes

None

External dependencies

None

Originally created by @alehaa on GitHub (Feb 16, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.2.3 ### Feature type Change to existing functionality ### Proposed functionality The official NetBox repository contains actions to perform certain tasks periodically, such as updating the translations. I suggest restricting these periodic actions to using the official repository only: ``` if: github.repository == ‘netbox-community/netbox’ ``` An alternative might be to check if the required authentication tokens are available for those cronjob actions, so that forks can still use those actions. ### Use case Actions should be enabled in forks to run test cases. While this is beneficial, periodic actions often send emails, e.g. about missing tokens. Restricting these actions to NetBox upstream would concentrate the actions where they are needed and avoid error messages in forks. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: housekeeping labels 2025-12-29 21:35:47 +01:00
adam closed this issue 2025-12-29 21:35:48 +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#10773
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?