-
-
Notifications
You must be signed in to change notification settings - Fork 3
feature(@videndum/release-mastermind): HasConflict trigger #219
Copy link
Copy link
Open
Labels
Context - Release MastermindRelated to @resnovas/release-mastermindRelated to @resnovas/release-mastermindStatus - AvailableThis issue is available for either Developers or Community contributors to developThis issue is available for either Developers or Community contributors to developType - FeatureA new featureA new feature
Metadata
Metadata
Assignees
Labels
Context - Release MastermindRelated to @resnovas/release-mastermindRelated to @resnovas/release-mastermindStatus - AvailableThis issue is available for either Developers or Community contributors to developThis issue is available for either Developers or Community contributors to developType - FeatureA new featureA new feature
Type
Projects
Status
Available
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:
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.