Fix the mergeback workflow #534
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
Merge main into v1
Merge main into v1
…t-pip-v1 Prevent accidental analysis of the `get-pip.py` script. [v1 cherry-pick]
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
…s: latest` Always test against both the default and latest CodeQL bundle. This improves test coverage shortly after a CodeQL bundle release, where the latest bundle may not yet be built into the Actions VM image as the default bundle. It also saves a manual step during bundle release testing, since we no longer need to temporarily change the PR checks to `tools: latest`. There is some redundancy when the latest bundle is the same as the default bundle on the VM image, but this can be considered a test for the `tools: latest` configuration.
Create a prerequisite job that runs the init step twice, with `tools: null` and `tools: latest`. Use the outputs of these steps to compare the two CodeQL versions. Pass the list of distinct tool versions for the integration tests to use in their matrix strategy. This avoids redundant test jobs when the default and latest bundles are actually the same version of CodeQL. `~` is accepted by JSON but not by the Actions context language, so we use `null` to indicate the default version.
Create a prerequisite job that runs the init step twice, with `tools: null` and `tools: latest`. Use the outputs of these steps to compare the two CodeQL versions. Pass the list of distinct tool versions for the analysis job to matrix over. This lets us test the analysis against both versions, while avoiding duplication when they are actually the same version.
This allows users to specify a different token for retrieving the codeql config from a different repository. Fixes github/advanced-security-field#185
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
Merge main into v1
This was referenced Apr 25, 2023
This was referenced Apr 26, 2023
This was referenced Apr 27, 2023
This was referenced Apr 28, 2023
This was referenced Apr 29, 2023
This was referenced Jun 21, 2023
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.
And manually mergeback v1 into main.
Needed to do a few fixes here:
post-release-mergeback.ymlworkflowversionscript so that newlines are correctly stripped to keepremoveNPMAbsolutePathshappyMerge / deployment checklist