Fork using only a single branch or tag #10983

Closed
opened 2025-11-02 09:23:57 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @sad75 on GitHub (Jun 7, 2023).

Feature Description

Fork is an important operation in some development processes. It will be much more convenient if the resulting repository will contain only the useful references and not all the ones from the original repository.

As it is possible with github , it could be achieved by selecting a branch or a tag for the clone operation.

Screenshots

image

Originally created by @sad75 on GitHub (Jun 7, 2023). ### Feature Description Fork is an important operation in some development processes. It will be much more convenient if the resulting repository will contain only the useful references and not all the ones from the original repository. As it is possible with [github ]( https://github.blog/changelog/2022-07-27-you-can-now-fork-a-repo-and-copy-only-the-default-branch/), it could be achieved by selecting a branch or **a tag** for the clone operation. ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/6814287/b2552a47-aef2-4cea-8a05-c7cb0dbb449d)
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 09:23:57 -06:00
Author
Owner

@dsseng commented on GitHub (Jul 10, 2023):

Working on it right now

/assign @sh7dm

@dsseng commented on GitHub (Jul 10, 2023): Working on it right now /assign @sh7dm
Author
Owner

@dsseng commented on GitHub (Jul 11, 2023):

Implemented support to fork arbitrary branch, since some projects are developed not on the default branch

@dsseng commented on GitHub (Jul 11, 2023): Implemented support to fork arbitrary branch, since some projects are developed not on the default branch
Author
Owner

@dsseng commented on GitHub (Jul 11, 2023):

Extra idea: maybe we should support the same option for migrations? It's maybe even more useful in such case when people migrate (essentially fork a repo to their instance) for development purpose

@dsseng commented on GitHub (Jul 11, 2023): Extra idea: maybe we should support the same option for migrations? It's maybe even more useful in such case when people migrate (essentially fork a repo to their instance) for development purpose
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10983