Enum Blocking 

pub enum Blocking {
    No,
    Yes,
    Conflict,
    Unsaid,
}

Whether a failing check actually stands between the pull request and main, according to the forge.

The rollup lists every check equally, so coverage going red on a repository that deliberately does not require it looked exactly like a broken build - and magi answered by spending a fix round on a change that was fine. Pull request 37 had to be merged by hand for that reason: the only red check was editorconfig, which was failing because the action could not fetch its own binary, and which the repository does not require.

mergeStateStatus is where GitHub applies the required-check set, so it is the one field that can tell the difference.

Variants

No

Required checks are satisfied and the branch merges cleanly.

Yes

Something required is failing or missing.

Conflict

The branch no longer merges: the base moved under it.

Unsaid

The forge did not say - an older gh, or a token without the scope. Treated as Yes, because refusing to guess is the rule everywhere else in this module.

Implementations

impl Blocking

pub fn stops_a_merge(self) -> bool

Does this stand between the pull request and the base branch?

Trait Implementations

impl Clone for Blocking

fn clone(&self) -> Blocking

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for Blocking

impl Debug for Blocking

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Eq for Blocking

impl PartialEq for Blocking

fn eq(&self, other: &Blocking) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for Blocking