Thanks for posting the link! It looks like you’ve already managed to figure it out but just to leave the answer here for any others that end up in a similar situation:

It looks like your project uses a build and deploy step that’s defined in your package.json file.

VivekJadeja/VivekJadeja.github.io/blob/0c064ef41a8e7d91668ec5d4efff01ea743b02fb/package.json#L24

  "react-bootstrap": "^1.3.0",
  "react-dom": "^16.13.1",
  "react-router-bootstrap": "^0.25.0",
  "react-router-dom": "^5.2.0",
  "react-scripts": "3.4.3",
  "react-spring": "^8.0.27"
},
"scripts": {
  "start": "react-scripts start",
  "predeploy": "npm run build",
  "deploy": "gh-pages -d build",
  "build": "react-scripts build",
  "test": "react-scripts test",
  "eject": "react-scripts eject"
},
"eslintConfig": {
  "extends": "react-app"
},
"browserslist": {
  "production": [
    ">0.2%",

I believe that the issue you were seeing was because you pushed the changes you made to the master branch of your repository but didn’t run this deploy step after, meaning the built version of your site wasn’t pushed to your gh-pages branch that serves your site’s code. To make sure this doesn’t happen again in future you’ll need to run npm run deploy after pushing the latest changes to your master branch.