Fork a repository
There is a Git server utilized by the Nautilus project teams. Recently, a new developer named Jon joined the team and needs to begin working on a project. To begin, he must fork an existing Git repository. Follow the steps below:
-
Click on the Gitea UI button located on the top bar to access the Gitea page.
-
Login to Gitea server using username jon and password Jon_pass123.
-
Once logged in, locate the Git repository named sarah/story-blog and fork it under the jon user.
Steps
Pretty simple and straight forward.
- Login into UI with given user password
- CLick on the repository (at right sidebar)
- Click on the fork option (top right)
Good to Know?
Git Forking Concepts
- Purpose: Create personal copy of someone else’s repository
- Independence: Fork is separate from original repository
- Contribution: Common workflow for open source contributions
- Ownership: You own and control your fork
Fork vs Clone
- Fork: Server-side copy (GitHub, GitLab, Gitea)
- Clone: Local copy on your machine
- Relationship: Fork maintains connection to original
- Workflow: Fork → Clone → Modify → Pull Request
Collaboration Workflow
- Fork: Create your copy of the repository
- Clone: Download fork to local machine
- Branch: Create feature branch for changes
- Commit: Make and commit your changes
- Push: Upload changes to your fork
- Pull Request: Propose changes to original repository
Gitea Features
- Self-hosted: Git service similar to GitHub
- Lightweight: Minimal resource requirements
- Web Interface: User-friendly repository management
- Collaboration: Issues, pull requests, wikis