Yaron Kaikov

> > * **[actions] Add a check for backport labels**: As part of the Automation of ScyllaDB backports project, each PR should get either a `backport/none` or `backport/X.Y` label. Based...

> > includes the four conditions before we open a backport pr: > > > > * PR should be closed > > * PR should have the proper label....

> > This PR includes 3 commits: > > ``` > > * **[actions] Add a check for backport labels**: As part of the Automation of ScyllaDB backports project, each...

> Adding the link to the requirement document: https://docs.google.com/document/d/1vQEGNFzsqA1VZjwkWYpf4n3FlNmff3m8izCidl5vdwU/edit?usp=sharing > > In section 4: Once PR is closed and the fix is promoted, the backported PR for the relevant release...

> > This PR includes 3 commits: > > ``` > > * **[actions] Add a check for backport labels**: As part of the Automation of ScyllaDB backports project, each...

@scylladb/scylla-maint Can we merge this? (I know we are in a merge freeze but this PR is only about GitHub actions that are not related to CI regression)

> > @scylladb/scylla-maint Can we merge this? (I know we are in a merge freeze but this PR is only about GitHub actions that are not related to CI regression)...

@avikivity Did we finish with the merge freeze? can we get it in?

@scylladb/scylla-maint please merge

@avikivity Can you please review