Proposal to allow forking to same namespace when forking via WEB
As per @sean_carroll recommendation, I am creating this issue as an enhancement proposal.
Creating a fork in the same namespace is possible only via API after !26062 Merge but back then it wasn't possible when forking via UI because, according to @pshutsin "alternative name & path couldn't be provided at that time. As I understand now we have an ability to alternate name & path in UI so we can allow forking to the same namespace via UI too. Looks like new improvement issue"
Also according to him, "it shouldn't be hard to do"
I am requesting/proposing to make this improvement in order to
- Unify the behavior between API and UI
- Allow users to, when necessary, fork a project to the same namespace, since not many users can or know how to take advantage of the API in order to achieve it
Scenario that triggered this need:
On a project I'm working on we need to create a seed repository that will then be used by many teams as the base to build their own solutions... We need to keep track of which teams have forked from our seed (only forking allows us to do that), and some of those teams belong to the same namespace as the seed we are creating