-
-
Notifications
You must be signed in to change notification settings - Fork 470
chore: ci bump (fixes #1168) #1259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mirkosalvato1-ctrl
wants to merge
1
commit into
codeaashu:main
Choose a base branch
from
mirkosalvato1-ctrl:oslifeguard/ci_bump-1168-1784789047
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+3
−3
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: codeaashu/DevDisplay
Length of output: 516
🌐 Web query:
actions/checkout v4 persist-credentials defaults GitHub token local git configuration💡 Result:
In
actions/checkout@v4, thepersist-credentialsinput defaults totrue[1][2][3]. When set totrue(default), the action configures theGITHUB_TOKEN(or the provided personal access token/SSH key) in the local git configuration [2][4]. Specifically, it writes anhttp.{url}.extraheadersetting containing an authorization header directly into the local.git/configfile [4][5]. This persistence allows subsequent steps in the same workflow job to perform authenticated git commands (such as pushing commits or fetching submodules) without needing to manually re-authenticate [2][5]. Whenpersist-credentialsis set tofalse, the action skips this configuration, which prevents these credentials from being written to the.git/configfile [4][5]. This is often recommended as a security best practice to minimize the risk of credential leakage (e.g., if the repository workspace, including the.gitdirectory, is accidentally uploaded as a job artifact) [6][5]. Note that ifpersist-credentialsis left at its default oftrue, the persisted git configuration can take precedence over other authentication methods, such asgh auth setup-git[4]. If you do not require subsequent steps to have authenticated git access, settingpersist-credentials: falseis the recommended approach to opt out [2][4][5].Citations:
gh auth setup-gitdoes not override the git user following anactions/checkoutinvocation cli/cli#10905persist-credentials: falseon checkout steps cli/go-gh#225persist-credentials=trueplease actions/checkout#2312Disable persisted checkout credentials across all workflows.
actions/checkout@v4persists the GitHub token in local Git config by default. Setpersist-credentials: falseat each checkout unless the job explicitly needs authenticated Git operations:.github/workflows/JSONchecker.yml#L13-L13.github/workflows/greetings.yml#L16-L16.github/workflows/issue-reminder.yml#L11-L11🧰 Tools
🪛 zizmor (1.26.1)
[warning] 13-13: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
📍 Affects 3 files
.github/workflows/JSONchecker.yml#L13-L13(this comment).github/workflows/greetings.yml#L16-L16.github/workflows/issue-reminder.yml#L11-L11🤖 Prompt for AI Agents
Source: Linters/SAST tools