Repository navigation
ci: add org-shared ci.yml alongside legacy workflows - #384
Merged
Merged
Conversation
promote(develop->main): umbrella 2.30.2 release-prep — drop 120MB blob + reconcile leaf pins
The operative legal terms (sections 0-17) already govern under AGPL-3.0; this only removes the FSF template's generic "or any later version" placeholder from the non-operative How-to-Apply section, matching pyproject.toml's license = "AGPL-3.0-only" declaration.
chore(release): promote develop → main
release: promote SciTeX 2.30.9 to main
Staged migration step 1: land the thin caller ALONGSIDE legacy files. Legacy files stay until branch protection moves to shared contexts and a PR proves the published check names. No behavior change yet.
Member
Author
|
CI note: the new shared quality-audit gate reports 58 pre-existing violations (orphan tests, sphinx bundle, undeclared imports, print usage) unrelated to this ci.yml addition. These need a separate fix PR from the python team; this PR only lands the caller. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Staged migration step 1 (no behavior change): land thin org-reusable caller alongside legacy files. Legacy deletion + protection update follow after a PR proves the published check names.