Setting default options for manual backport comments
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
recently we noticed that when commenting on an issue @Mergifyio backport branch-xx will create the PR even in presence of conflicts.
Is it possible to change the default behaviour to avoid creating the PR if there are conflicts in the configuration file?
Or we'll have to always add --ignore-conflicts=false manually?
Looking at the documentation we can't find a way to set default options for manual commands.
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the documentation for manual backport commands and the configuration file used by comment-triggered backports. Trace how --ignore-conflicts=false is handled and determine where command defaults are defined. Done means the desired conflict behavior can be configured without repeating the option manually, with documentation covering the setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100