Day 30 (Git Hard Reset) - Checker fails despite correct reset and push

Git for Beginners
,
#1

Subject: Day 30 (Git Hard Reset) - Checker fails despite correct reset and push

Hi KodeKloud Support,

I’m working through the 100 Days of DevOps challenge and have hit a persistent issue on the “Git Hard Reset” task (Day 30) across multiple repo instances (games, official, apps).

Task requirement: Reset the git commit history in the given repo so only two commits remain - “initial commit” and “add data.txt file” - then push the changes.

What I did (consistent across all three attempts):

  1. SSH’d into ststor01 as natasha
  2. cd into the target repo path
  3. Ran git config --global --add safe.directory to resolve the dubious ownership warning
  4. Ran git log --oneline --all to find the hash for the “add data.txt file” commit
  5. Ran git reset --hard (used sudo/chown to resolve an index.lock permission denied error)
  6. Verified git log --oneline showed exactly two commits: initial commit and add data.txt file
  7. Fixed safe.directory for the bare repo at /opt/.git (same dubious ownership error)
  8. Ran chown -R natasha:natasha on both the working repo .git directory and the bare repo
  9. Ran git push -f origin master - succeeded with “forced update”
  10. Verified both git log --oneline (working repo) and git --git-dir=/opt/.git log --oneline (bare repo) showed identical, matching two-commit history
  11. Confirmed git status showed “working tree clean” and “up to date with origin/master”

Despite all of the above matching exactly what’s described in the task and in other community write-ups of this same challenge, clicking Check consistently returns:

“required data not found under repo, seems like repository was not reset properly”

This has now happened on three separate repo instances of this same task, each time with git state verified correct on both local and remote. This suggests either:

  • The checker script may be validating against a stale/cached repo state
  • The checker may be looking for something beyond commit count/hash matching that isn’t documented in the task description

Could you please look into why the checker is failing when the git history and remote state both appear correct? Happy to provide terminal screenshots for each step if helpful.

Thanks,
Victor

#2

I think you’ve over-complicated it.
You should not be changing ownership of any files or directories. The repo belongs to root so become root before executing any git commands:

sudo -i

Then, hard reset to the correct commit hash and force push. That should be it.

#3

Thank you I have done it :+1::white_check_mark:

Appreciate your response… we keep moving on to the next task :fire::fire::fire::pray::pray: