-
Notifications
You must be signed in to change notification settings - Fork 309
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
Merge releases/v3 into releases/v2 #2289
Conversation
Typically, we warn when there is no `push` trigger in the workflow file that triggered this run. However, when this action is triggered by a `workflow_call` event, we assume there is a custom process for triggering the action and we don't want to warn in this case.
Specifies the versions of the action, CLI and GHES that are jointly compatible.
As opposed to being killed by the JVM, which is a failure not a user error.
Mergeback v3.25.4 refs/heads/releases/v3 into main
Run release process using Python 3.12
Add more user errors
Avoid warning on workflow_call triggers
Co-authored-by: Henry Mercer <henrymercer@github.com>
This prevents them from being truncated.
…liability This lets us achieve some performance and reliability improvements for workflows that run autobuild directly without specifying a build mode.
Add a compatibility table to the README
…g-improvements End tracing in autobuild Action for workflows that don't specify a build mode
Disable `fail-fast` for PR checks
Add support for on-demand feature flags
Merge main into releases/v3
Pushed a commit to update the checked-in dependencies. Please mark the PR as ready for review to trigger PR checks. |
Hello, don't know how useful my review on this would be, but happy to do a review if needed. I do have a question though, just to build my understanding of our process: This is the PR that adds the new features to the release branch correct? Assuming it gets merged, this means that anyone using the |
On second thoughts, I had a look at the diff, and this appears to be just a sync PR, needing just a stamp. Happy to give it to unblock us. |
That's right — currently we bring all the latest features from v3 into v2 (apart from Node 20 support), and to do that we have a backport PR like this each time we release the CodeQL Action. Usually it's automatically generated, but this one updated a workflow file, and updating workflow files requires a PAT, so we had to run it manually. Thanks for the review! |
Merging b7cec75 into
releases/v2
.Conductor for this PR is @henrymercer.
Contains the following pull requests:
fail-fast
for PR checks #2283 (@henrymercer)Please do the following:
releases/v2
branch.Create a merge commit
is selected rather thanSquash and merge
orRebase and merge
.