src/lib.rs re-exported one adapter under a vendor-neutral name:
pub use syncode_runner_control_gitea::protocol;
Every other re-export in that file names what it is — engine, source_git, github_actions. This one promised a neutrality the module does not have: it is
the Gitea Connect family, and src/cli/control.rs maps SynCode, Gitea and
Forgejo onto GiteaFamily while rejecting GitHub and GitLab explicitly.
The name is now gitea_protocol, and the ten call sites in src/cli* and tests/ follow. Nothing else changes: no types, no behaviour, no public
surface beyond the module path.
Doing it now costs a rename. After a second control-plane adapter lands, crate::protocol could not mean both, so it would cost a rename plus a
migration of whatever had grown on the ambiguous name in the meantime.
Ran locally: cargo fmt --check, cargo clippy --workspace --all-targets --all-features -- -D warnings, scripts/check-architecture.sh, scripts/check-rust-loc.sh. The test suite runs in the validation stage of the
image build.
Closes #21.
`src/lib.rs` re-exported one adapter under a vendor-neutral name:
pub use syncode_runner_control_gitea::protocol;
Every other re-export in that file names what it is — `engine`, `source_git`,
`github_actions`. This one promised a neutrality the module does not have: it is
the Gitea Connect family, and `src/cli/control.rs` maps SynCode, Gitea and
Forgejo onto `GiteaFamily` while rejecting GitHub and GitLab explicitly.
The name is now `gitea_protocol`, and the ten call sites in `src/cli*` and
`tests/` follow. Nothing else changes: no types, no behaviour, no public
surface beyond the module path.
Doing it now costs a rename. After a second control-plane adapter lands,
`crate::protocol` could not mean both, so it would cost a rename plus a
migration of whatever had grown on the ambiguous name in the meantime.
Ran locally: `cargo fmt --check`, `cargo clippy --workspace --all-targets
--all-features -- -D warnings`, `scripts/check-architecture.sh`,
`scripts/check-rust-loc.sh`. The test suite runs in the validation stage of the
image build.
`crate::protocol` promised a neutrality the module does not have: it is the
Gitea Connect family, and the CLI maps only SynCode, Gitea and Forgejo onto it
while rejecting GitHub and GitLab. Every other re-export in lib.rs names what it
is.
Renaming now is a rename. After a second control-plane adapter it would also be
a migration of whatever grew on the ambiguous name.
day01
merged commit a1cbc8ee36 into %!s()2026-08-03 13:51:59 +00:00
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.
Closes #21.
src/lib.rsre-exported one adapter under a vendor-neutral name:Every other re-export in that file names what it is —
engine,source_git,github_actions. This one promised a neutrality the module does not have: it isthe Gitea Connect family, and
src/cli/control.rsmaps SynCode, Gitea andForgejo onto
GiteaFamilywhile rejecting GitHub and GitLab explicitly.The name is now
gitea_protocol, and the ten call sites insrc/cli*andtests/follow. Nothing else changes: no types, no behaviour, no publicsurface beyond the module path.
Doing it now costs a rename. After a second control-plane adapter lands,
crate::protocolcould not mean both, so it would cost a rename plus amigration of whatever had grown on the ambiguous name in the meantime.
Ran locally:
cargo fmt --check,cargo clippy --workspace --all-targets --all-features -- -D warnings,scripts/check-architecture.sh,scripts/check-rust-loc.sh. The test suite runs in the validation stage of theimage build.