Skip to content

Commit 4c89408

Browse files
authored
chore: update codeql target for v7.1.x (#4903)
1 parent f7ea421 commit 4c89408

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

.github/workflows/codeql.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ name: "CodeQL"
22

33
on:
44
push:
5-
branches: [ "main", "5.x" ]
5+
branches: [ "main", "v7.1.x" ]
66
pull_request:
7-
branches: [ "main", "5.x" ]
7+
branches: [ "main", "v7.1.x" ]
88

99
jobs:
1010
analyze:

etc/notes/releasing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ release-please automatically tags release commits with a tag in the format v<maj
3232

3333
Then, backport the release action to the target release branch. This should be done as the first PR on the release branch. Use the following instructions to create it.
3434

35-
First, create a copy of our current release action (release.yml). Then, change any references to `main` to the target branch. Double check that there isn't any release tooling on `main` that doesn't exist on the target branch. If there is, make sure this is backported too. After opening the PR, check the CI to make sure everything works as expected: add backports of CI fixes as needed.
35+
First, create a copy of our current release action (release.yml). Then, change any references to `main` to the target branch. Also, add the branch to the list of CodeQL target branches (codeql.yml). Double check that there isn't any release tooling on `main` that doesn't exist on the target branch. If there is, make sure this is backported too. After opening the PR, check the CI to make sure everything works as expected: add backports of CI fixes as needed.
3636

3737
Once the release action PR is merged, release-please will work on this branch in the same way as it does on `main`. Any PRs that merge to the release branch trigger the release action and update the release PR that release-please manages. Proceed as normal from here.
3838

0 commit comments

Comments
 (0)