Skip to content
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

Allow unstable branches to be merged #25

Merged
merged 8 commits into from
Mar 6, 2024
Merged

Allow unstable branches to be merged #25

merged 8 commits into from
Mar 6, 2024

Conversation

Bullrich
Copy link
Contributor

@Bullrich Bullrich commented Mar 6, 2024

Added the ability to merge unstable branches.

This is enabled by default, as GitHub's Auto Merge feature always merges unstable branches.

Fixes #24

@Bullrich Bullrich self-assigned this Mar 6, 2024
@Bullrich Bullrich requested a review from a team as a code owner March 6, 2024 13:40
@Bullrich Bullrich linked an issue Mar 6, 2024 that may be closed by this pull request
@Bullrich Bullrich changed the title Unstable branches Allow unstable branches to be merged Mar 6, 2024
Bullrich added a commit to Bullrich/polkadot-fellows-runtimes that referenced this pull request Mar 6, 2024
This upgrade contains the change in paritytech/auto-merge-bot#25 which fixes the problem with unstable branches.

## The problem

When the `/merge` command is triggered on a PR that still can't be merge, the bot enables auto-merge.

**But**, when the command is run when the PR is ready to merge, the action will fail to enable auto-merge (this is expected).

We evaluate the error message, and if it says that the PR is clean, it simply merges the PR.

But, we did not handle `unstable` PRs.

An unstable PR is a PR that _can be merged, but a **non required status check is failing**._

So, if a user invoked the `/merge` command on a PR that was ready to merge, but a not-required status check was failing, it would crash.

This upgrade fixes this problem.
Copy link
Contributor

@rzadp rzadp left a comment

Choose a reason for hiding this comment

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

LGTM

@Bullrich Bullrich merged commit dc2eac9 into main Mar 6, 2024
9 checks passed
@Bullrich Bullrich deleted the unstable-branches branch March 6, 2024 16:26
@mordamax
Copy link

mordamax commented Mar 6, 2024

may be that should've been optional param during merge request? so that's not always allowing unstable, but only if developer sure during current request?

like /merge --allow-unstable

does it allow to merge only not required unstable? or all kinds of ?

fellowship-merge-bot bot added a commit to polkadot-fellows/runtimes that referenced this pull request Mar 18, 2024
This upgrade contains the change in paritytech/auto-merge-bot#25 which
fixes the problem with unstable branches.

## The problem

When the `/merge` command is triggered on a PR that still can't be
merge, the bot enables auto-merge.

**But**, when the command is run when the PR is ready to merge, the
action will fail to enable auto-merge (this is expected).

We evaluate the error message, and if it says that the PR is clean, it
simply merges the PR.

But, we did not handle `unstable` PRs.

An unstable PR is a PR that _can be merged, but a **non required status
check is failing**._

So, if a user invoked the `/merge` command on a PR that was ready to
merge, but a not-required status check was failing, it would crash.

This upgrade fixes this problem.

### Other upgrades

#### `get-fellows-action` has been upgraded to `1.1.0`

This new version contains:
- paritytech/get-fellows-action#15
  - Fixed a bug where candidates (`rank 0`) counted as fellows.
  - Now we filter anyone whose rank is below 1.
- paritytech/get-fellows-action#16
- Fixes a problem where a fellow using a superidentity wouldn't appear.
- This is a particular case that I discovered with @joepetrowski not
appearing as a fellow.
- This error was also encountered in review bot and fixed in
paritytech/review-bot#107
- paritytech/get-fellows-action#11
  - We upgraded the system to work with `papi` and with `smoldot`.
  - We are **bleeding edge** now!


#### replaced token generation script for github's

We replaced the action used to generate a token from a github app,
originally `tibdex/github-app-token` for
`actions/create-github-app-token`

It is more safe to use an action that has been developed by github
themselves than by an external party.

---

- [x] Does not require a CHANGELOG entry

---------

Co-authored-by: fellowship-merge-bot[bot] <151052383+fellowship-merge-bot[bot]@users.noreply.github.com>
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.

Allow merge of unstable branches
3 participants