3362620ee3
On the @Forgejo instance of Codeberg, we discovered that forking a repo which is already forked now returns a 500 Internal Server Error, which is unexpected. This is an attempt at fixing this. The error message in the log: ~~~ 2023/05/02 08:36:30 .../api/v1/repo/fork.go:147:CreateFork() [E] [6450cb8e-113] ForkRepository: repository is already forked by user [uname: ...., repo path: .../..., fork path: .../...] ~~~ The service that is used for forking returns a custom error message which is not checked against. About the order of options: The case that the fork already exists should be more common, followed by the case that a repo with the same name already exists for other reasons. The case that the global repo limit is hit is probably not the likeliest. Co-authored-by: Otto Richter <otto@codeberg.org> Co-authored-by: Giteabot <teabot@gitea.io> |
||
---|---|---|
.. | ||
blob.go | ||
branch.go | ||
collaborators.go | ||
commits.go | ||
file.go | ||
fork.go | ||
git_hook.go | ||
git_ref.go | ||
hook.go | ||
hook_test.go | ||
issue.go | ||
issue_attachment.go | ||
issue_comment.go | ||
issue_comment_attachment.go | ||
issue_dependency.go | ||
issue_label.go | ||
issue_reaction.go | ||
issue_stopwatch.go | ||
issue_subscription.go | ||
issue_tracked_time.go | ||
key.go | ||
label.go | ||
language.go | ||
main_test.go | ||
migrate.go | ||
milestone.go | ||
mirror.go | ||
notes.go | ||
patch.go | ||
pull.go | ||
pull_review.go | ||
release.go | ||
release_attachment.go | ||
release_tags.go | ||
repo.go | ||
repo_test.go | ||
star.go | ||
status.go | ||
subscriber.go | ||
tag.go | ||
teams.go | ||
topic.go | ||
transfer.go | ||
tree.go | ||
wiki.go |