We got "Pull request with merge commit are not supported" on one of our backport requests, what's the right way to solve this (using mergify preferably)?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
We got "Pull request with merge commit are not supported" on one of our backport requests, what's the right way to solve this (using mergify preferably)?
And question: that seems like bad grammar - is it possible someone has hijacked or hacked our mergify account? (The bad grammar being typically one would prefix the non-distinct singular noun "merge commit" with "a", or make it plural, so either "with a merge commit" or "with merge commits" would be better).
Originally posted by @qneill-sifive in https://github.com/Mergifyio/mergify/discussions/5063
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
No repository file, test, or entry point is named. Start by locating the handling for backport requests and searching for the exact “Pull request with merge commit are not supported” message; determine the supported Mergify workflow and whether the wording is incorrect. Done means a reproducible explanation or fix is documented and covered by an appropriate test if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100