sync.py pushes main from the home to github fast-forward only, and github's main has commits the home doesn't. Nothing was overwritten. Either bring those commits to the home (a branch and a PR), or replace github's history: Actions → sync → Run workflow with force.
DONE: github's main follows the home again and this sync run is green.
sync.py pushes `main` from the home to github fast-forward only, and github's `main` has commits the home doesn't. Nothing was overwritten. Either bring those commits to the home (a branch and a PR), or replace github's history: Actions → sync → Run workflow with `force`.
DONE: github's `main` follows the home again and this sync run is green.
Expected: github's main is the old proof-of-concept history, kept on GitHub as archive/poc-main (e85709ec), so it gets replaced once with the force input. The first forced run (1094) was refused by GitHub: the deploy key was added through gh, GitHub holds such a key to that OAuth app's scopes, and the authorization lacks workflow, so a push touching .github/workflows/ is rejected. The owner is approving the workflow scope (device flow); the key is then re-added under it and the forced sync re-run. This issue closes when GitHub main equals Teahub main.
Expected: github's `main` is the old proof-of-concept history, kept on GitHub as `archive/poc-main` (e85709ec), so it gets replaced once with the force input. The first forced run (1094) was refused by GitHub: the deploy key was added through `gh`, GitHub holds such a key to that OAuth app's scopes, and the authorization lacks `workflow`, so a push touching `.github/workflows/` is rejected. The owner is approving the `workflow` scope (device flow); the key is then re-added under it and the forced sync re-run. This issue closes when GitHub `main` equals Teahub `main`.
Settled. gh's authorization gained workflow, the deploy key was re-added under it (166898032, write, this repo only), and the forced sync (run 1098) replaced GitHub's main: out {'main': 'forced'}. GitHub main is now 745231844f, the same as Teahub main. The old history stays on GitHub as archive/poc-main (e85709ec). From here main goes out fast-forward only on every push and every 15 minutes.
Settled. `gh`'s authorization gained `workflow`, the deploy key was re-added under it (166898032, write, this repo only), and the forced sync (run 1098) replaced GitHub's `main`: `out {'main': 'forced'}`. GitHub `main` is now 745231844f64, the same as Teahub `main`. The old history stays on GitHub as `archive/poc-main` (e85709ec). From here `main` goes out fast-forward only on every push and every 15 minutes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sync.py pushes
mainfrom the home to github fast-forward only, and github'smainhas commits the home doesn't. Nothing was overwritten. Either bring those commits to the home (a branch and a PR), or replace github's history: Actions → sync → Run workflow withforce.DONE: github's
mainfollows the home again and this sync run is green.Expected: github's
mainis the old proof-of-concept history, kept on GitHub asarchive/poc-main(e85709ec), so it gets replaced once with the force input. The first forced run (1094) was refused by GitHub: the deploy key was added throughgh, GitHub holds such a key to that OAuth app's scopes, and the authorization lacksworkflow, so a push touching.github/workflows/is rejected. The owner is approving theworkflowscope (device flow); the key is then re-added under it and the forced sync re-run. This issue closes when GitHubmainequals Teahubmain.Settled.
gh's authorization gainedworkflow, the deploy key was re-added under it (166898032, write, this repo only), and the forced sync (run 1098) replaced GitHub'smain:out {'main': 'forced'}. GitHubmainis now745231844f, the same as Teahubmain. The old history stays on GitHub asarchive/poc-main(e85709ec). From heremaingoes out fast-forward only on every push and every 15 minutes.