Skip to content

velnor-new: require rust-required (new Rust CI) alongside Required - #61

Draft
donbeave wants to merge 4 commits into
mainfrom
velnor-new-rust-required
Draft

donbeave wants to merge 4 commits into
mainfrom
velnor-new-rust-required

Conversation

@donbeave

@donbeave donbeave commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Sets the required checks of tailrocks/velnor-new to DCO, Required, Required verdict, and rust-required, per the owner's transition decision (2026-11-18) on tailrocks/velnor-new#604. This replaces the earlier ci-required rename on this branch.

Naming. During the transition the new Rust workflow keeps its check name rust-required, and the old engine's ci.yml keeps reporting Required and Required verdict. The rename to a single check name happens later, when velnor-new#608 removes the old engine's Rust CI path. So velnor-new's required contexts become:

  • rust-required — produced by the new Rust workflow
  • Required — produced by the old ci.yml
  • Required verdict — produced by the old ci.yml
  • DCO

Required verdict. It is a live required context of velnor-new's protect-main ruleset 24396608 today, so it stays required here. It must be re-confirmed at the single-name rename: if no workflow reports it once the old engine's Rust CI path is gone, it must be dropped from this list.

What changes. The velnor-new entry of repository_policies in variables.tf now reads required_checks = ["DCO", "Required", "Required verdict", "rust-required"], replacing the ci-required variant this branch carried.

Applying. The owner applies this terraform only after velnor-new's #1223 is green on main, so rust-required is reported by the new workflow before it becomes mandatory. Requiring it earlier would block merges on a context no run reports yet.

🤖 Generated with Claude Code

donbeave and others added 2 commits November 18, 2026 04:11
Add "rust-required" to the required checks of tailrocks/velnor-new. It is
the context the new generator's rust-ci.yml reports (tailrocks/velnor-new#604,
step 7). The existing "Required" and "Required verdict" contexts of the live
protect-main ruleset 24396608 stay required.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com>
…uired

Per the owner decision after tailrocks/velnor-new#604: the new rust-ci.yml
reports "Required" and the old ci.yml renames its aggregate check to
"ci-required". Require both plus DCO and the kept "Required verdict";
drop the separate rust-required addition.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com>
@donbeave donbeave changed the title velnor-new: require the rust-required check velnor-new: require Required (rust-ci) and ci-required (old ci.yml) Nov 17, 2026
…-new

Owner decision 2026-11-18: during the transition the new Rust workflow
keeps its "rust-required" check name and the old ci.yml keeps
"Required" and "Required verdict"; the rename to a single name waits
for tailrocks/velnor-new#608 removing the old engine's Rust CI path.
Drop the "ci-required" rename and require DCO, Required, Required
verdict and rust-required.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com>
@donbeave donbeave changed the title velnor-new: require Required (rust-ci) and ci-required (old ci.yml) velnor-new: require rust-required (new Rust CI) alongside Required Nov 17, 2026
Keep #62's velnor-new merge_queue block and the existing required checks.
Strict stays at its default (false). This branch only adds DCO and
rust-required to velnor-new required_checks.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com>
@donbeave

Copy link
Copy Markdown
Contributor Author

Updated onto #62; must not be applied until velnor-new's #1223 merges, since rust-required only exists after it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant