fix: only generate SBOM on protected branches, only commit on main - #4
Merged
Merged
Conversation
SBOM generation now only runs on main, beta, and development branches. The SBOM commit/push step only runs on main to prevent bot commits on feature branches and PRs.
This was referenced Mar 17, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
main,beta, anddevelopmentbranches (was running on every push to any branch)main— onbetaanddevelopmentthe SBOM is generated and validated but not committed backContext
The standalone
sbom.ymlworkflows in individual app repos (opencatalogi, openconnector, softwarecatalog, mydash, docudesk) are being replaced withenable-sbom: truein the reusable quality workflow to avoid duplication.Test plan
mainbetaanddevelopment(generate + validate only, no commit)feature/**branches