### Problem to solve Currently, the "Repository > Forks" is not configurable per project via the API. ### Proposal Allow `Repository > Forks` to be configured via the api. ### Intended users Devon the Devops Engineer would use this in conjunction with Pulumi (or other Infrastructure configuring tools), to setup and maintain the correct settings across multiple gitlab repositories. ### User experience goal What is the single user experience workflow this problem addresses? A devops engineer should be able to use the API with GitLab to enable and disable the `Repository > Forks` feature on a per-project basis.