Skip to content

feature(@videndum/release-mastermind): HasConflict trigger #219

@TGTGamer

Description

@TGTGamer

Discussed in TGTGamer/SCAA#218

Originally posted by ssfxate September 9, 2021
Hey, thank you for the great GH action. I really happy with it.

Is it possible to label a PR due to occured conflict with the a branch?

Current response:

Originally posted by **TGTGamer** September 11, 2021 So looking through the API documentation, the simple method I was hoping would work doesn't have an endpoint that I can use. What I would need to do is compare the commits on all the pull requests and test for a conflict that way.

This information has been documented here: https://stackoverflow.com/questions/34011782/how-to-resolve-conflict-with-merging-with-github-api

I will add it to the backlog to do, however, I have other higher priority issues to address first, which will enable much-needed functionality in this action.

I will aim to have this in progress by the end of the month, once other git actions have been enabled within the action.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Context - Release MastermindRelated to @resnovas/release-mastermindStatus - AvailableThis issue is available for either Developers or Community contributors to developType - FeatureA new feature

    Type

    No type

    Projects

    Status

    Available

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions