Repository navigation
feat: add mask-token option - #142
Open
LucaGuerra wants to merge 1 commit into
Open
LucaGuerra wants to merge 1 commit into
LucaGuerra wants to merge 1 commit into
Conversation
LucaGuerra
force-pushed
the
add-mask-token
branch
from
October 16, 2026 08:43
46f0779 to
294e906
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
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.
Some legacy workflows require passing a token between jobs, so the producing job needs an option to disable the default security masking of the output. It can then be masked by the receiving job. A typical example of this is the legacy slsa generator https://github.com/slsa-framework/slsa-github-generator/tree/main that some repositories still rely on but this can happen with some other complex reusable workflow setups.
In this PR, I propose adding said option. Of course, the default is still masked and this is not a breaking change as all existing users will continue to work in the same way.