Fix existing forks that have higher repository access levels than their parents
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
In #36662 (closed), we are fixing the behavior on new forks that will be created. Existing forks will still behave the old way.
For existing forks to behave the same way as new forks, we'll need to fix their project_features records and copy the repository access level related attributes from their parent.
Edited by 🤖 GitLab Bot 🤖