Don't default the base repo for pull requests to "origin"#5508
Merged
stefanhaller merged 1 commit intomasterfrom Apr 13, 2026
Merged
Don't default the base repo for pull requests to "origin"#5508stefanhaller merged 1 commit intomasterfrom
stefanhaller merged 1 commit intomasterfrom
Conversation
When no base repository is configured using gh, we have several heuristics for choosing a likely base repo before prompting the user. One of these was that if the origin remote exists, we'd choose that. This may be the right choice in some cases, but in many others it's not; for example, in the common scenario of a forking setup where the upstream repo's remote is called after its owner, and the fork remote is called origin, we would choose origin as the base repo, which results in not showing any PRs. Don't do that, and instead prompt the user for the base repo in this case.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
🟢 Coverage 0.00% diff coverage
Metric Results Coverage variation Report missing for 9cd5fb81 Diff coverage ✅ 0.00% diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (9cd5fb8) Report Missing Report Missing Report Missing Head commit (4218f97) 61937 53901 87.03% Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#5508) 2 0 0.00% Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%1 Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
TIP This summary will be updated as you push new changes. Give us feedback
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this pull request
Apr 15, 2026
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [jesseduffield/lazygit](https://github.com/jesseduffield/lazygit) | patch | `v0.61.0` → `v0.61.1` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>jesseduffield/lazygit (jesseduffield/lazygit)</summary> ### [`v0.61.1`](https://github.com/jesseduffield/lazygit/releases/tag/v0.61.1) [Compare Source](jesseduffield/lazygit@v0.61.0...v0.61.1) <!-- Release notes generated using configuration in .github/release.yml at v0.61.1 --> This release has just a few fixes for the recently added GitHub pull requests feature. #### What's Changed ##### Enhancements 🔥 - Hide closed pull requests on main branches by [@​stefanhaller](https://github.com/stefanhaller) in [#​5501](jesseduffield/lazygit#5501) ##### Fixes 🔧 - Normalize repository owner casing to fix GitHub MR integration by [@​bradly0cjw](https://github.com/bradly0cjw) in [#​5495](jesseduffield/lazygit#5495) - Don't default the base repo for pull requests to "origin" by [@​stefanhaller](https://github.com/stefanhaller) in [#​5508](jesseduffield/lazygit#5508) ##### Maintenance ⚙️ - Security fix: avoid using `${{ }}` variable interpolation in `run:` steps by [@​orbisai0security](https://github.com/orbisai0security) in [#​5487](jesseduffield/lazygit#5487) - Add a justfile by [@​stefanhaller](https://github.com/stefanhaller) in [#​5490](jesseduffield/lazygit#5490) #### New Contributors - [@​orbisai0security](https://github.com/orbisai0security) made their first contribution in [#​5487](jesseduffield/lazygit#5487) - [@​bradly0cjw](https://github.com/bradly0cjw) made their first contribution in [#​5495](jesseduffield/lazygit#5495) **Full Changelog**: <jesseduffield/lazygit@v0.61.0...v0.61.1> </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMTMuMCIsInVwZGF0ZWRJblZlciI6IjQzLjExMy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiLCJhdXRvbWF0aW9uOmJvdC1hdXRob3JlZCIsImRlcGVuZGVuY3ktdHlwZTo6cGF0Y2giXX0=-->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When no base repository is configured using gh, we have several heuristics for choosing a likely base repo before prompting the user. One of these was that if the origin remote exists, we'd choose that. This may be the right choice in some cases, but in many others it's not; for example, in the common scenario of a forking setup where the upstream repo's remote is called after its owner, and the fork remote is called origin, we would choose origin as the base repo, which results in not showing any PRs. Don't do that, and instead prompt the user for the base repo in this case.