Backport v2.26.8 574aaa581 to v2 #2493
Merged
Conversation
This file contains 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
Previously, we uploaded SARIF artifacts in the `analyze-post` step and database and log artifacts in the `init-post` step. As we migrate to the updated `artifact` dependencies, we want to switch to uploading all artifacts in one step. In order to upload all artifacts in one go and maintain the artifacts at the root of the debug directory, we first move SARIF artifacts to the database directory. This should not affect any other consumers of the SARIF file as this occurs in the `init-post` step.
Previously, we uploaded combined SARIF artifacts in both the `analyze-post` and `upload-sarif-post` steps. This change ensures that these artifacts are uploaded at most once — in `analyze-post` if it is a first-party run and `upload-sarif-post` if it is a third-party run. This is a defensive check because as we upgrade to the new `artifact` dependencies we will not be able to upload artifacts to the same artifact directory.
More accurately describes what these artifacts are, rather than the step they're uploaded in.
Mergeback v3.26.7 refs/heads/releases/v3 into main
Co-authored-by: Andrew Eisenberg <aeisenberg@github.com>
Fix incorrect documentation about the `token` input to the Actions.
The script `.github/update-release-branch.py` uses the `git` command to push changes. Therefore we need to ensure that `git` authenticates with a token that has the `workflows` write permision. This change restore the GitHub token used by the script to access the API and applies the `workflows` write permission to the token used by `git`.
…cts-upload Refactor: prepare debug artifacts for `artifact` upgrades
…-for-auth Use generated token on checkout
…ct-robustness Improve the robustness of creating and uploading debug artifacts
…er-logging Improve logging when preparing and uploading debug artifacts
…nings Turn URI errors into warnings
Update default bundle to 2.19.0
Merge main into releases/v3
GITHUB_TOKEN is no longer defined; we should use either the workflow token or the app one. Here we try using the app one.
…n-to-backport Backport workflow: try using the app token
This reverts commit 81dc191.
This reverts commit 8c041af.
github-actions
bot
removed
the
Update dependencies
|
Pushed a commit to update the checked-in dependencies. Please mark the PR as ready for review to trigger PR checks. |
henrymercer
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Manual mergeback because https://github.com/github/codeql-action/blob/main/.github/workflows/update-release-branch.yml is not currently able to create a backport PR.
The branch was created by https://github.com/github/codeql-action/actions/runs/10939964997/job/30371403063 in the normal way, but PR creation failed because the app token doesn't have pr-creation rights.