Lost pull request who used "Squash and merge"
See original GitHub issueThanks for this great tool!
Too bad PRs that are merged with “Squash and merge” are not outputted in the changelog. Is this something that could be fixed?
Using the following command:
github-changes -o nlog -r nlog -a --only-pulls --use-commit-body
e.g. this one is missing: https://github.com/NLog/NLog/pull/1628
when using github-changes -o nlog -r nlog -a --use-commit-body
(no --only-pulls
) is somewhat there:
- [1bc8400](https://github.com/NLog/NLog/commit/1bc84001f3eab6175948bffd24168bb01048fc19) allow different separator for Exception.Data (#1628) (@FroggieFrog)
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Github "Squash and Merge" - subsequent pull request ...
The main thing you're doing wrong is continuing to use a branch after it has been merged. After you merge, delete the branch....
Read more >How to see the original commits in PR after Squash Merge
The only way to access the original commits would be by not deleting the source branch when you merge, and then view them...
Read more >Why I'm against merging pull requests in squash mode or ...
In merge mode, an ugly sideway out-and-in retains all details in developing the feature. · In squash mode, changes are combined into a...
Read more >Prevent completing PR (Pull-Request) with a squash merge ...
However when the pull-request contains a merge-commit, and when then completing the pull-request with a squash-merge (this usually happens by accident), this ...
Read more >Squashing Your Pull Requests - Cloud Four
As a general rule, when merging a pull request from a feature branch with a messy commit history, you should squash your commits....
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
@304NotModified you can just point the package to a git branch and it should take care of that. check out - http://stackoverflow.com/questions/17509669/how-to-install-nodejs-package-from-github-directly
discussion continues in #64