forking project doesn't copy issues/wiki/pipeline settings
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
When you fork a project that has issues, pipeline & wiki disabled, the new project gets them enabled.
(Environment: GitLab EE 8.13.0-ee gitlab-ce@562bbc61f9656bc96ba7dbd2f10afcff21428e0b)
To reproduce:
Fork a project. In our case, an internal visibility one with issues, pipeline & wiki disabled.
Expected result:
A new project with issues/pipeline/wiki disabled by default.
Actual result:
A new project with issues/pipeline/wiki enabled
(Alternatively, a way to specify the default settings for a new project would also work - I've search for such a setting but not managed to find it.)
The way it currently is, all our projects get cluttered with functionality we don't use and/or have the potential to confuse users.
(Our company follows a "forking" workflow - i.e. each developer has a fork of the whole repo, and sends merge requests from that repo back to the main repo.)