Closed
Conversation
mtfishman
force-pushed
the
mf/v2-noop-verify
branch
from
b7d305a to
57221ad
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #177 +/- ##
=======================================
Coverage 78.68% 78.68%
=======================================
Files 12 12
Lines 793 793
=======================================
Hits 624 624
Misses 169 169
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Member
Author
|
Verification successful — all required-context checks reported under their new v2 names ( |
mtfishman
added a commit
to ITensor/ITensorPkgSkeleton.jl
that referenced
this pull request
May 4, 2026
## Summary Migrates this repo's own workflow callers AND the workflow templates to the renamed shape from `ITensorActions v2.0.0`. Two parallel sets of changes (in `.github/workflows/` and `template/.github/workflows/`) kept in sync per CLAUDE.md convention. ## What changes For each of the 12 standard workflow files (caller copy + template copy): - Workflow `name:` matches the file's basename (e.g. `FormatCheck.yml` → `name: "FormatCheck"`). Drops cases like `"Format Check"`, `"Integration Test Request"`, `"Register Package"`. - Job display `name:` also matches the filename for single-job workflows. - Job key is kebab-case lowercase, with brand names like `tagbot`/`compathelper` treated as single words rather than split on internal capitals (`Register` → `registrator`, `compat-helper` → `compathelper`, etc.). - `uses: ITensor/ITensorActions/.github/workflows/X.yml@v1` → `@v2`. - `FormatCheckComment.yml` `workflow_run.workflows:` trigger updated from `["Format Check"]` to `["FormatCheck"]` to match the renamed parse-phase workflow. The end-state of the templates matches what `SparseArraysBase.jl`'s `main` already carries (verified live in ITensor/SparseArraysBase.jl#177 — every required-context check from the new v2 ruleset reported under its new name and SUCCESS). Patch version bumped to `0.3.59`. ## Rollout follow-up Once this lands, the next step is the `ITensorOrgPatches` sweep that copies these templates into the rest of the standard repo set, and the matching ruleset updates (replacing old context names with new ones in each repo's branch ruleset).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Trivial no-op .gitignore tweak to exercise PR-event workflows under the new ITensorActions v2 caller-side renames + matching ruleset contexts. Will be closed once CI confirms the new context strings match the new ruleset's required-status-checks.