Allow contributions to the todo branch#2145
Merged
dscho merged 1 commit intomaingitgitgadget/gitgitgadget:mainfrom Feb 22, 2026
quick-fix-for-MaintNotesgitgitgadget/gitgitgadget:quick-fix-for-MaintNotesCopy head branch name to clipboard
Merged
Allow contributions to the todo branch#2145dscho merged 1 commit intomaingitgitgadget/gitgitgadget:mainfrom quick-fix-for-MaintNotesgitgitgadget/gitgitgadget:quick-fix-for-MaintNotesCopy head branch name to clipboard
todo branch#2145dscho merged 1 commit intomaingitgitgadget/gitgitgadget:mainfrom
quick-fix-for-MaintNotesgitgitgadget/gitgitgadget:quick-fix-for-MaintNotesCopy head branch name to clipboard
Conversation
The `todo` branch is completely divergent from Git's `master` branch, and as such contains different files. Yet it still belongs to the Git project... This is needed to fix the `Unrecognized project` error in https:// github.com/git/git/pull/2209 The underlying logic was correct until c72d162 (project-options: handle shallow worktrees gracefully, 2024-01-01) broke it; This change was needed to allow migrating from running on a self-hosted Azure Pipelines runner to running on hosted GitHub Actions runners, but the logic was incomplete and would no longer reliably detect whether GitGitGadget is running in a PR that targets the Git project. Another fix would have been to move forward with the `vars.CONFIG` idea championed in #1991. However, my attention was directed away from that effort for a long time now, and it won't be _so_ easy to push that over the finish line. Let's unblock the contributor first. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
github-actions bot
pushed a commit
to Bassamx93/gitgitgadget
that referenced
this pull request
Feb 22, 2026
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
1 participant
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.
The
todobranch is completely divergent from Git'smasterbranch, and as such contains different files. Yet it still belongs to the Git project...This is needed to fix the
Unrecognized projecterror in https:// github.com/git/git/pull/2209The underlying logic was correct until c72d162 (project-options: handle shallow worktrees gracefully, 2024-01-01) broke it; This change was needed to allow migrating from running on a self-hosted Azure Pipelines runner to running on hosted GitHub Actions runners, but the logic was incomplete and would no longer reliably detect whether GitGitGadget is running in a PR that targets the Git project.
Another fix would have been to move forward with the
vars.CONFIGidea championed in #1991. However, my attention was directed away from that effort for a long time now, and it won't be so easy to push that over the finish line. Let's unblock the contributor first.