Issue Summary

• Creating a fork from a commit no longer allows creation of the fork, the following error is encountered:

  "We had trouble creating your fork."
  

This is reproducible on Data Center: no

Steps to Reproduce

1. Gain READ access to a private repository
2. Edit and make a change to a file in the repository source, then click "Commit"
3. When prompted to create a fork due to not having WRITE access, finalize by clicking "Commit"
4. Error is encountered, no fork is created

Expected Results

• When a user does not have WRITE access to a repository, they should still be able to make changes to files
• It is expected that a fork of the repo would be created with a resulting PR to merge the changes into the parent repo upon approval

Actual Results

• The user instead encounters a 404/500 error and they are not able to commit any changes

Workaround

• Currently, there is no known workaround for this behavior. A workaround will be added here when available