Skip to content

ci: [Backport] backport-verification test #3393

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

Merged
merged 2 commits into from
Apr 11, 2025

Conversation

michalChrobot
Copy link
Collaborator

Backport

This is a backport of #3385

@michalChrobot michalChrobot self-assigned this Apr 11, 2025
@michalChrobot michalChrobot merged commit a6b889e into develop Apr 11, 2025
7 of 41 checks passed
@michalChrobot michalChrobot deleted the backport-information-in-pr-test-develop branch April 11, 2025 21:37
michalChrobot added a commit that referenced this pull request Apr 11, 2025
Due to nature of NGO of having 2 development branches (`develop` for
NGOv1.X and `develop-2.0.0` for NGOv2.X) we need to ensure that relevant
changes are landing in only one branch (when it's relevant to only
develop-2.0.0 for example) or both of them.

For people not familiar with NGO structure (but also for us) it might be
easy to omit the fact of making a backport (or forward port) so this PR
includes a GitHub workflow that will check if "**## Backport**" section
exist in the PR thus making it mandatory. This will add a bit of work to
each PR but it will ensure that developers get reminded about backports
and hopefully this will lead to

- Easier PR tracking since every PR will contain a description of a
backport or reasoning why a backport is not needed
- Reduction of potential forgotten backports which in turn could
increase overall quality of NGO

I tested this workflow on my fork of NGO repo and seems to be working as
expected

## Backport
Backport created in
#3393.
After this PR gets approved I will modify branch protection rules to
block PRs from merging if this check fails.

---------

Co-authored-by: Emma <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant