Show base commit in PRs (and not just the base branch)
See original GitHub issuePRs show the base branch, but they don’t tell how long ago the current branch was updated. Example:
master A-B-C-D-E
\
feature-branch C-Q-Z
In this case, this feature would tell us that C
is the real base
I’ve wanted to know this in the past, but at the moment I’m only thinking of why we shouldn’t implement this: 😅
- Our
update-pr-from-base-branch
feature already tells us whether it’s up to date and it allows us to update it
Discussion welcome. Would this info be useful? When?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Changing the base branch of a pull request - GitHub Docs
Under your repository name, click Pull requests. · In the "Pull Requests" list, click the pull request you'd like to modify. · Next...
Read more >GitHub pull request showing commits that are already in target ...
Here's a good workaround. Use the Edit button when viewing the PR in GitHub to change the base branch to something other than...
Read more >More ways to keep your pull request branch up-to-date
To update by rebasing, click the drop down menu next to the Update Branch button, click Update with rebase, and then click Rebase...
Read more >Using stacked pull requests in GitHub - LogRocket Blog
To stack two PRs, checkout the first branch from your base master (or develop ) and push your changes. ... Create the PR...
Read more >Set base commit - Feature Requests - Codecov
This will allow you to set any SHA to be the base commit. Currently, in a pull request it uses where you branched...
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
OK we need to merge #6103 first and then I can work on it
Love it. I didn’t know where to display it, but that makes sense. We can figure out the exact design later