jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
The mirror can push one commit twice within a second. GitHub starts two runs and cancels the older; that run's report job posted failure, and Gitea's github job failed the check before the surviving run passed (seen on ihasmail #17).
A cancelled run now posts nothing and leaves the result to the run that superseded it. Failures still report failure; tag runs are never cancelled.
The mirror can push one commit twice within a second. GitHub starts two runs and cancels the older; that run's `report` job posted **failure**, and Gitea's `github` job failed the check before the surviving run passed (seen on ihasmail #17).
A cancelled run now posts nothing and leaves the result to the run that superseded it. Failures still report failure; tag runs are never cancelled.
The mirror can push one commit twice in quick succession. GitHub then
starts two runs and cancels the older, and that run's report job posted
"failure" for the commit. Gitea's github job, seeing the newest status,
failed the check while the surviving run was still building and later
passed.
A cancelled run now posts nothing and leaves the result to the run that
superseded it. A real failure still reports failure.
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.
The mirror can push one commit twice within a second. GitHub starts two runs and cancels the older; that run's
reportjob posted failure, and Gitea'sgithubjob failed the check before the surviving run passed (seen on ihasmail #17).A cancelled run now posts nothing and leaves the result to the run that superseded it. Failures still report failure; tag runs are never cancelled.