DAM-static-site/DAM-README.md
peskyadmin 99d5e7b464
Some checks are pending
Deploy Hugo site to Pages / build (push) Waiting to run
Deploy Hugo site to Pages / deploy (push) Blocked by required conditions
repo usage
2025-03-25 21:14:38 -04:00

1.2 KiB
Raw Permalink Blame History

git remote add private http://gitea.damconsulting.net:3000/peskyadmin/DAM-static-site.git

  1. Check Your Current Remote Since youve cloned a project, it already has one remote configured (usually named origin). You can verify this by running: bash

git remote -v

This will show the URL of the public repository you cloned from (e.g., https://github.com/user/public-repo.git).

  1. Add a Second Remote To push to your private repository, you need to add it as a new remote. Lets call it private. Run: bash

git remote add private http://gitea.damconsulting.net:3000/peskyadmin/DAM-static-site.git

git remote -v shows remotes

  1. Pull from the Public Remote To keep your local repository updated with changes from the public remote, use: bash

git pull origin main

Replace with the branch youre working on (e.g., main or master). This fetches and merges updates from the public repo into your local branch.

  1. Push to the Private Remote After making your changes locally and committing them (with git add and git commit), you can push them to your private repository: bash

git push private main

This sends your commits to the specified branch in your private repo, not the public one.