Support creating mirrors that are up to date with the source repository
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
- Domain
- backend
Research direction
No files or tests are named; start by tracing the mirror-creation entry point and how it selects the fork or source project. Done means newly created private mirrors are current with the source while handling cases where the source is private or inaccessible to the GitHub App or user.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
When mirrors are created their main branch is always up to date with the fork they are created from but not the source project. This makes it so that often times users are required to update the fork or their mirror manually to ensure that they have the latest changes.
Describe the solution you'd like
When a mirror is being created, private mirrors should reference the source project instead of the fork or bring the fork up to date first.
Describe alternatives you've considered
GitHub actions could be set up on the organization that contains the forks to ensure that all forks are kept up to date.
Additional context
This logic will need to account for situations where the source project is private and not accessible by the private mirrors GitHub app or alternatively not accessible by the user.
- 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
-
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
-
[Bug] PUT /profiles/{id} silently drops design_prompt — designed voice profiles cannot be editedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
eventua11y/eventua11y.com#982 ·
Maintainers usually reply within 1 day