Any changes to an archived project will result in a 403
Summary
Attempting to open up a merge request with a fork parent that is archived will result in a 403.
Steps to reproduce
- Create a project and fork
- Archive the parent fork
- Create a merge request with the parent fork
- User will be re-directed to a 403 page.
What should happen
I'm not sure if a 403 is the correct response, as this could easily happen to users who have a lot of forks. Perhaps a flashing error message that details that the project is archived?
Edited by Cindy Pallares 🦉