Clarify documentation on installation and repo migration #1

Fluffinity commented 2026年06月15日 23:38:47 +02:00

Below are the commit messages explaining the contents of this PR.
The change to the build instructions is unrelated to the added
documentation on repo migration, so if a separate PR is wished
I can split it up. I included it here to reduce the overhead from
having to go through multiple PRs.

Inform users about migration issues with Github

Github has removed its API endpoint for migrating repositories. Trying
to access it results in the HTTP status code 410 Gone. Lets inform
users about that problem until some solution has been found.

Clarify repo migrations

This just explicitly states that only Forgejo instances are supported
targets of a repo migration

Fix instructions to compile from source

Without the --locked argument cargo may use newer versions of the
dependencies, which can cause build failures. So it's best to always use
that argument.

Below are the commit messages explaining the contents of this PR. The change to the build instructions is unrelated to the added documentation on repo migration, so if a separate PR is wished I can split it up. I included it here to reduce the overhead from having to go through multiple PRs. Inform users about migration issues with Github : Github has removed its API endpoint for migrating repositories. Trying to access it results in the HTTP status code `410 Gone`. Lets inform users about that problem until some solution has been found. Clarify repo migrations : This just explicitly states that only Forgejo instances are supported targets of a repo migration Fix instructions to compile from source : Without the `--locked` argument cargo may use newer versions of the dependencies, which can cause build failures. So it's best to always use that argument.