100 Days of Devops---- Day 23: Fork a Git Repository Unlock

KodeKloud Engineer
#1

“Cloned /opt/demo.git to /usr/src/kodekloudrepos as natasha with no sudo/permission changes. Verified .git directory created, origin remote correctly set, ownership natasha:natasha throughout. Source repo has zero commits (confirmed via HEAD/refs/heads/master with no refs), so ‘clone appears empty’ warning is expected, not an error. Checker still reports ‘not cloned’ — reproduced this exact same failure across 3 separate attempts on this task pattern (/opt/cluster.git and /opt/demo.git as source).”

#2

This doesn’t sound like Day 23 to me, which looks like this:

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:

  1. Click on the Gitea UI button located on the top bar to access the Gitea page.

  2. Login to Gitea server using username jon and password Jon_pass123.

  3. Once logged in, locate the Git repository named sarah/story-blog and fork it under the jon user.

Note: For tasks requiring web UI changes, screenshots are necessary for review purposes. Additionally, consider utilizing screen recording software such as loom.com to record and share your task completion process.

If that’s the task you’re doing, then you don’t need to do anything on the file system of the task – everything can be done within the Gitea UI – in fact, that’s the only way you can do this.