Gitea Migration: Quick Start Guide

Please follow these steps to get started and migrate your development workflow from GitHub to Gitea.

1. Log In to Gitea

• Visit our Gitea instance at: https://git.mslabs.in
• Click on "Sign In with MicrosoftEntraID".
• If it's your first login, an account will be created automatically.
• Ensure you are logged in and your account is active.

2. Find Your Repositories

• Open the shared Google Sheet provided to you all.
• Find all repositories you work on, your new repository URLs are listed under the "Gitea HTTP URL" and "Gitea SSH URL" columns.

3. Update Repository URLs Locally

Verify the current remote URL

Run this command in your repository folder to see the current remote URL:

git remote -v

Expected output should show both fetch and push URLs pointing to your current GitHub repository, for example:

origin  https://github.com/mslpro/iob-nest-api.git (fetch)
origin  https://github.com/mslpro/iob-nest-api.git (push)

There are two ways to update the Git remote URL in your local project:

Method 1: Edit .git/config Directly

Open the .git/config file in your project directory and update the url value:

[remote "origin"]
    url = https://git.mslabs.in/your-org/your-repo.git

Method 2: Use Git Command

Run this command in your repository folder:

git remote set-url origin https://git.mslabs.in/your-org/your-repo.git

Replace https://git.mslabs.in/your-org/your-repo.git with the new repository address as listed in the Google Sheet.

Verify Change to Remote URL

After updating the URL, verify it with:

git remote -v

Expected output should show both fetch and push URLs pointing to your new Gitea repository, for example:

origin  https://git.mslabs.in/your-org/your-repo.git (fetch)
origin  https://git.mslabs.in/your-org/your-repo.git (push)

Test Authentication & Connectivity

Fetch from the new remote to test authentication and connection:

git fetch

This command will prompt for authentication if needed (using PAT for HTTP or SSH keys for SSH URLs) and verify connectivity to the new Gitea instance.

4. Authentication Options (For Remote Development Only)

• For HTTP URLs:
  • Use a Personal Access Token (PAT) generated in your Gitea profile settings.

• For SSH URLs:

  • Use ed25519 SSH keys generated by:

    ssh-keygen -t ed25519
    

• Add your SSH public key (~/.ssh/id_ed25519.pub) to your Gitea profile under Settings > SSH / GPG Keys.

Windows Users

• If you are unfamiliar with SSH, use HTTP authentication.
• Tokens/passwords are securely stored in Windows Credentials Manager for seamless access.

Linux Users

• Generate SSH keys as above and add the public key to Gitea.
• SSH authentication works only with the "New SSH URL" from the Google Sheet.
• HTTP authentication requires a PAT for push and pull actions.

5. Commit & Branch Rules

• Direct pushes to main, dev, uat, and prod branches are locked.
• Always create new branches (e.g., feature/some-feature, fix/bug).
• Open Pull Requests (PR) from your branch to the protected branch.
• Project Managers review and merge your code.
• Use lowercase with dashes (-) or slashes (/) in branch names.

Examples:

• feature/auth-module
• fix/login-bug

Need Help?

If you face any issues during the migration process or repository access, feel free to contact the durga@mslabs.co.in in Teams for assistance.