Mirror runs driven by pairs.
The scheduler and the mirror pipeline still read the old githubConfig and giteaConfig. The pair enabled flag and every option in the pair form are saved to mirror_pairs and never read. A run should take a pair: source server for the fetch, target server for the push, pair options instead of the global config. This is the big refactor in gitea.ts.
**Mirror runs driven by pairs.**
The scheduler and the mirror pipeline still read the old `githubConfig` and `giteaConfig`. The pair `enabled` flag and every option in the pair form are saved to `mirror_pairs` and never read. A run should take a pair: source server for the fetch, target server for the push, pair options instead of the global config. This is the big refactor in `gitea.ts`.
<!-- github-sync-id:5331783882 -->
There is no mirror_pairs table on main. Runs are driven by the source and destination columns on each repository row. Closing, details on #390.
There is no mirror_pairs table on main. Runs are driven by the source and destination columns on each repository row. Closing, details on #390.
<!-- github-comment-id:5522248878 -->
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.
Mirror runs driven by pairs.
The scheduler and the mirror pipeline still read the old
githubConfigandgiteaConfig. The pairenabledflag and every option in the pair form are saved tomirror_pairsand never read. A run should take a pair: source server for the fetch, target server for the push, pair options instead of the global config. This is the big refactor ingitea.ts.There is no mirror_pairs table on main. Runs are driven by the source and destination columns on each repository row. Closing, details on #390.