[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [theia-dev] New feature enabled for CI: Require branches to be up to date before merging
|
Very cool, thank you.
I guess you need write access to the branch to be merged in order to see the "Update branch" button, right? Because it's your own branch or the contributor checked "allow edits from maintainers"?
/Thomas
------ Original Message ------
Date 23/03/2023 15:05:53
Subject [theia-dev] New feature enabled for CI: Require branches to be up to date before merging
Hi all,
Just to let you know that, as discussed in the last dev-meeting [1], we have enabled the "Require branches to be up to date before merging" feature for the CI in our main repository, on a "trial" basis of one month.
If your PRs are not based on the latest version of the master branch, merging will be blocked with message "This branch is out-of-date with the base branch", and an "Update branch" button will be available to rebase your PR so it's mergeable.
Note: Enabling this feature forced us to configure at least one on our "status checks" (workflow jobs) as being mandatory to pass: we have set "Lint" and "eclipsefdn/eca", partly because their job names are unlikely to change. If they do, a ticket will need
to be opened towards the Eclipse Foundation to also update the selected "status checks" under the feature, in the "Branch protection rule" settings page, for our master branch.
Please let me know if you encounter issues or have feedback about any of this.
Regards,
Marc
