-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
[BUG]: credential persistence through GitHub Actions artifacts #290
Comments
Hi @dcampbell24, thanks for the report. To make sure I understand: is the problem here that The reason we don't currently do that is a rendering limitation: emitting a multi-line annotation won't be very pretty or readable at the moment. An alternative here would be for us to emit |
Yeah, I tried it at first without the If you already have a warning[artipacked]: credential persistence through GitHub Actions artifacts
--> /home/...
|
113 | - name: checkout
| _______-
114 | | uses: actions/checkout@v4
115 | | with:
116 | | ref: ${{ github.ref_name }}
| |___________________________________- does not set persist-credentials: false
|
= note: audit confidence → Low instead of: warning[artipacked]: credential persistence through GitHub Actions artifacts
--> /home/...
|
113 | - name: checkout
114 | uses: actions/checkout@v4
115 | with:
116 | ref: ${{ github.ref_name }}
| ________-
| |___________________________________- does not set persist-credentials: false
|
= note: audit confidence → Low
Can you emit two annotations? One that says to add |
113 | - name: checkout
114 | uses: actions/checkout@v4
| ______-
| |___________________________________- does not set with: |
Change the order so the |
Hmm yeah, that might work -- in general multiple annotations on the same span don't flow super well, but I'll give that a try later today! |
Pre-submission checks
Expected behavior
It should tell you that you need
Actual behavior
Instead of
Reproduction steps
persist-credentials: false
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: