d-bis/proxmox
4
0
Fork 0
Code Issues 2 Pull Requests 13 Actions Packages Projects Releases Wiki Activity

docs(git): parity checklist before audit submission (origin/gitea/master)
Some checks failed
Deploy to Phoenix / validate (push) Has been cancelled
Details
Deploy to Phoenix / deploy (push) Has been cancelled
Details
Deploy to Phoenix / deploy-atomic-swap-dapp (push) Has been cancelled
Details
Deploy to Phoenix / cloudflare (push) Has been cancelled
Details

Browse Source 
Made-with: Cursor
This commit is contained in:
defiQUG
2026-04-28 01:18:23 -07:00
parent 2bc18871f5
commit cc074a8828
1 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
scripts/git/README-gitea-proxmox-sync.md
View File

@@ -21,3 +21,23 @@ Resolve by either:
Do **not** force-push to **gitea** unless you intend to rewrite shared history.
CyberSecur-related commits exist on **GitHub `origin`**; **gitea** may lack them until a successful merge and push.
## Parity check (e.g. before audit submission)
All three should match (same commit hash):
```bash
git fetch origin
git fetch gitea
git rev-parse master origin/master gitea/master
```
If local `master` lags but is a **fast-forward** behind (no local-only commits you need to keep), update and align:
```bash
git checkout master
git pull origin master --ff-only
# or: git merge --ff-only gitea/master
```
If you have uncommitted changes, **stash** first (`git stash push -u` if untracked files would be overwritten), then pull, then `git stash pop` as needed. After alignment, `git push origin master` and `git push gitea master` should report **up to date** when remotes already share the tip.