Mergify `squash` command lost an original author of commits
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Docs: https://docs.mergify.com/commands/squash/#parameters
When I as maintainer write a command @Mergifyio squash [<commit message format>] in comment for PR, I don't want be an author of new commit of this PR. I think it should be an author of PR not comment.
See https://github.com/playframework/playframework/pull/13044
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 with the squash command parameters in the linked Mergify documentation and inspect the referenced Play Framework pull request for the author-loss example. Trace the command's handling of commit authors and verify the result against a comparable pull request; done means squashing preserves the pull request author's authorship rather than assigning it to the commenter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100