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.

#3

Day 24: Git Create Branches

Facing same issue please help

#4

Here’s what to know about Day 24:

# Log into storage server and see who owns the repo
[natasha@ststor01 ~]$ ls -l /usr/src/kodekloudrepos/
total 4
drwxr-xr-x 3 root root 4096 Sep  4 20:55 blog

# It's owned by root, so become root and change dir into the repo:
[natasha@ststor01 ~]$ sudo -i
[root@ststor01 ~]# cd /usr/src/kodekloudrepos/blog/

# What's the state of the repo?
[root@ststor01 blog]# git status
On branch kodekloud_blog
nothing to commit, working tree clean

# We're currently in the kodekloud_blog branch, which is the wrong
# branch to fork from.  Let's change to branch master:
[root@ststor01 blog]# git checkout master
Switched to branch 'master'
Your branch is up to date with 'origin/master'.

# ...and create the new branch the task requests from us
[root@ststor01 blog]# git checkout -b xfusioncorp_blog
Switched to a new branch 'xfusioncorp_blog'

# Let's verify that we've done it.  You can also use "git status" for this.
[root@ststor01 blog]# git log --graph
* commit 8b19ce03b71658a18585569d13170b27d19d2e8e (HEAD -> xfusioncorp_blog, origin/master, master)
  Author: Admin <admin@kodekloud.com>
  Date:   Fri Sep 4 20:55:16 2026 +0000
  
      initial commit
[root@ststor01 blog]#