"squash and merge" commit message doesn't render clickable link
See original GitHub issueIs your feature request related to a problem? Please describe. Currently this app only parse pr number from normal merge commit. https://github.com/desktop/desktop/blob/72e87e23d3c8d5fd3ea9c6ab04f0f03b01968f38/script/changelog/parser.ts#L16-L21
It’d be nice to parse pr number from squash and merge
commit too.
Suggestion regex /\(#(\d+)\)$/
e.g. Update README.md (#123)
If this is accepted, i can help to contribute if team don’t have time.
Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
squash merge commit does not contain previous commit ...
All of the docs for Azure DevOps describe the squash merge setting the same. It takes the topic branch commits and merges them...
Read more >Configuring commit squashing for pull requests - GitHub Docs
On GitHub.com, navigate to the main page of the repository. · Under your repository name, click Settings. · Under "Pull Requests", select Allow...
Read more >Squash and merge - GitLab Docs
Go to the merge request, and scroll to the merge request reports section that contains the Merge button. Ensure the Squash commits checkbox...
Read more >MR squash is removing commit message details
I created an MR but when the MR was merged I can see the merge commit and my new commit with only the...
Read more >A fix for Gitlab squash commit message composition - Qubidu
Save the bookmark and go to the merge request you want to squash the commits in. Stay on the overview, leave it all...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@1pete aha, now I’m with you.
Not currently, but we have a bunch of tests in
app/test/unit/text-token-parser-test.ts
to catch regressions - here’s an example you can use in reference to reproduce this issue for that style of commit message:https://github.com/desktop/desktop/blob/0ec5b64ed393efbe43fb58abef39b43d83a9e12d/app/test/unit/text-token-parser-test.ts#L168-L190
@1pete I’ve updated the title to reflect the right context, and labelled this as a
bug
because it affects existing repositories