Important information about the Gitea migration

Most frequently asked questions about the Gitea migration and guides to get started. If you are missing something here please contact Gitea Project

What Serives are available?

GIT

Gitea is a barebone GIT service. It is a GitHub fork and therefore very similar to GitHub. https://gitea.psi.ch

Pages

You can publish your own gitpage within seconds! There is two ways described here how you can create your own gitpage:

Create a Repository called gitea-pages in your Organization with a second branch called gitea-pages. All content inside the gitea-pages branch will be automatically published under: {YourOrg}.pages.psi.ch If you want to have this content available in the internet, please open a SNOW ticket with your request and some justyfication about why that should be exposed to the internet.
Create a gitea-pages branch inside any repository, the content of that branch will be served at: {YourOrg}.pages.psi.ch/{YourRepo} Same rules for publishing apply to this method too.

Snippets

Since Gitea has no way to publish snippets we introduce snippets.psi.ch When you press "Continue with PSI Gitea account" the Auth token used with Gitea will be reused to login to snippets. (Also works if you have MFA enabled) Snippets can be read by anonymous users / services but only created by a logged in user.

Runners

We provide runners in every security zone, that you can wherever you are inside PSI-Network use the CI/CD from Gitea. If none of the runners available to your project suits you, you can contact Gitea Project and we can find a solution that fits you best. The runner RPM is available on repos.psi.ch and also as package to download in the Linux Organization on Gitea. https://gitea.psi.ch/linux/act-runner/packages

FAQ

My Project was migrated and I can't push anymore

This Project was archived and is now available on https://gitea.psi.ch Please use following commands to update your local git:

git remote -v
If the output starts with "origin https..." use option 1 otherwise 2

git remote set-url https://gitea.psi.ch/{Org}/{Repo}.git
git remote set-url git@gitea.psi.ch:/{Org}/{Repo}.git If you have not recieved a special notification about the archival the organization is the Gitlab group name.

More information about archived projects can be found here:

https://docs.gitlab.com/user/project/working_with_projects/#archive-a-project

I want to migrate a project from Gitlab / Github to Gitea

Login to https://gitea.psi.ch with your PSI LDAP account. (Username: muster_m Password: SUPERSECRET123) Since Gitea is a GitHub fork, you will find Organizations instead of groups. Every user is allowed to create Organizations. When should I create a new Organization? -> If you are (or feel) responsible for a certain team in PSI it makes sense to create an Organization named likewise. Try to use the official names used at PSI. In the top left corner you can click on browse and then Organizations to see if someone already created the desired organization.

Optional:

Click the "+" in the top right of your screen and create an organization
Authorization inside Organizations can be done via Teams - Create Team and give the persmissions you need
If you want to use AD Groups to authorize people in your Teams please contact Gitea Project

Migration:

Click the "+" in the top right of your screen and click "New Migration"
Choose the Source you want to migrate from
Enter the HTTPS clone URL
On the source you need to create an access token for that project
Paste the token in "Access Token"
Choose the migration options (Attention! If you choose mirror, you won't be able to migrate releases!)
Choose an Owner (Organization or if its a personal Project your Username) and give it a name. (Can be the existing one)

I had a collaboration with non PSI Users on gitlab.psi.ch

All "ext-" users have been imported as restricted users and must be explicitly added to a project. If you are missing a user and you are sure it has a PSI account, message Gitea Project

4.1 KiB Raw Blame History