Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`sync-pr-commit-title` renames PR to "Merge pull request #XXX from <branch>"
See original GitHub issueThanks to #1743, PRs are renamed to the merge commit title. However, that’s typically an uninformative message, such as “Merge pull request #XXX from <branch>” — the PRs then shouldn’t be renamed, but are, per the screenshot. The automated rename is
Blaisorblade changed the title
Complete supporting guarded pDOT: Allow paths as value definitions, try 2Merge pull request #155 from Blaisorblade/path-defs-rebase-2
(I later renamed this back by hand).
Disabling sync-pr-commit-title fixes the problem. Unfortunately, I’m only merging PRs in a private repo, so I can’t (yet) give a public link (but I should be able to, soon).
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ll limit this feature to squashing commits.
Fixed. At some point we’ll publish a new release. Currently we’re still waiting for the Chrome Web Store to publish the last update.