[FIX] Push sbom into master after merging via ssh#4636
Merged
Conversation
joragua
requested changes
Jul 9, 2025
jesmrec
force-pushed
the
fix/sbom_merged_into_master
branch
from
039ca77 to
a93bee4
Compare
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
2 participants
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.
Previous version tried to push the
sbom.jsonfile generated by CI to themasterbranch, but the branch protection rules prevented to perform such action. Current PR would fix that.Included:
SSH is used to perform the commit. To push the commit, an SSH public key and private key must be configured in the repository settings.
The current version of the SBOM is normalized and compared with the previous one. A commit is only made if differences are found.
If a commit is made, it will trigger another job, which will be skipped due to a condition defined in the job configuration.
@DeepDiver1975 you added a
DEPLOYMENT_SSH_KEYin Deploy Keys of Settings. That's the public key, it would be required to add the private key as repo secret as well. Other option: I created a pair of keys for testing and i could re-use them as keys by replacing yours.I think this solution will work, but, we'll not know until the PR is merged (SBOM commit is created).
An alternative considered was pushing the sbom.json file to each development branch, but it was ultimately discarded due to lower overall performance.
Related Issues
App:
ReleaseNotesViewModel.ktcreating a newReleaseNote()with String resources (if required)QA