Skip to content

[26.0 backport] github/ci: Check if backport is opened against the expected branch#47702

Merged
vvoland merged 1 commit intomoby:26.0from
vvoland:v26.0-47647
Apr 9, 2024
Merged

[26.0 backport] github/ci: Check if backport is opened against the expected branch#47702
vvoland merged 1 commit intomoby:26.0from
vvoland:v26.0-47647

Conversation

@vvoland
Copy link
Contributor

@vvoland vvoland commented Apr 9, 2024

- What I did
Added a GHA check for the expected target branch on backport PRs.

- How to verify it
CI: https://github.com/moby/moby/actions/runs/8466474413/job/23195302313?pr=47647
Tested with this PR titled as [1337.0 backport] github/ci: Check if backport is opened against the expected branch

Run branch=$(echo "[1337.0 backport] github/ci: Check if backport is opened against the expected branch" | sed -n 's/^\[\([0-9]*\.[0-9]*\) backport\].*/\1/p')
PR title suggests backport to 1337.0, but PR is opened against master
Error: Process completed with exit code 1.

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
(cherry picked from commit 61269e7)
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
@vvoland vvoland added status/2-code-review kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny area/testing area/project labels Apr 9, 2024
@vvoland vvoland added this to the 26.0.1 milestone Apr 9, 2024
@vvoland vvoland self-assigned this Apr 9, 2024
Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vvoland vvoland merged commit 9db1b6f into moby:26.0 Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/project area/testing kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny status/4-merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants