Enable branch creation as part of syncing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github, typescript
Research direction
Start by tracing the syncing flow and the mirror-creation flow, then review issue #445 for the related branch condition. Done means syncing recreates a missing fork branch, can continue afterward, and no longer creates that branch during mirror creation; verify both paths with the repository's existing checks.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
In cases where the fork branch that corresponds to a mirror has been renamed or deleted, the syncing function will fail to execute instead of creating the desired branch.
Describe the solution you'd like
During syncing, any missing fork branch should be recreated to allow the sync to continue and provide a way for users to reset a conflicted fork branch. This change would also make it unnecessary to create the fork branch during mirror creation so that logic should be removed.
Describe alternatives you've considered
Alternatively the deletion or renaming of a fork branch could be disallowed through protections on the fork or could result in the corresponding mirror being renamed / deleted.
Additional context
There is currently a bug detailed in #445 that makes this situation more common.
- Dominant language
- TypeScript
- Stars
- 203
- Forks
- 42
- Avg merge
- 1h 15m
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github-community-projects/private-mirrors
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github-community-projects/private-mirrors#525 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/private-mirrors#524 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-2 days Newbie friendliness 68/100
github-community-projects/private-mirrors#449 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
github-community-projects/private-mirrors#485 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github-community-projects/private-mirrors#481 ·
Maintainers usually reply within 1 day
All issues in github-community-projects/private-mirrors
Similar issues
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
blamechris/chroxy#9272 ·
Maintainers usually reply within 1 day
-
no-repo-link tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 66/100
BraveOPotato/NoSignups#2458 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
drmrd/vernacular#1061 ·
Maintainers usually reply within 1 day