Hey, I removed/replaced the last commit, because of a mistake. Sorry for misunderstanding :)
Cheers, Alex On Wed, Jun 26, 2024 at 4:25 PM Alan D. Salewski <ads@salewski.email> wrote: > Hi Folks, > > I maintain a GitHub mirror of the the GNU Screen git repo here: > > https://github.com/salewski/screen-mirror > > During a recent sync attempt[0] I encountered the following error: > > Fetching origin > From https://git.savannah.gnu.org/git/screen > + 49917a7...4b52c01 master -> master (forced update) > Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 > remote: error: GH006: Protected branch update failed for > refs/heads/master. > remote: error: Cannot force-push to this branch > To github.com:salewski/screen-mirror.git > ! [remote rejected] master -> master (protected branch hook declined) > error: failed to push some refs to 'github.com: > salewski/screen-mirror.git' > > It looks to me like commit 49917a7d9466584e9214e21d5a2fae9d40ebcbfc > was replaced by commit b4e5968f0b7ad7673a57c11b91f359139418f4c0 > (evidence of a Git 'forced push') and that the only difference is a > detail in the commit message. The (two-line) patch content looks > identical to me, and 'git diff' agrees. > > Is there anything else to be aware of from a Git repo maintenance > perspective? > > Just want to be sure.... > > Thanks, > -Al > > > [0] Basically just: > git remote update origin > Followed by: > git push --mirror gh-mirror > > > -- > a l a n d. s a l e w s k i > ads@salewski.email > salew...@att.net > https://github.com/salewski > >
