ci: harden contributor checks#254
Merged
Merged
Conversation
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
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.
Summary
lint,unit tests,integration tests, andpackage buildso each can be required independently.make packageto build the sdist/wheel and smoke-test importing the built wheel.make teststays green on local Python 3.13/macOS while preserving the real POSIX lock behavior.mainbranch protection baseline and required status checks.Verification
Local results:
make lint: passedmake package: builteveros-1.0.0sdist/wheel and imported the wheel as1.0.0make ci: passed, including 1178 unit tests and 57 integration testsRemote PR checks are green:
CI / lintCI / unit testsCI / integration testsCI / package buildDocs / linksCommit lint / commit messagesBranch protection
mainis now configured with strict required status checks for the six always-emitted contexts above. Dependabot config validation is documented as optional/advisory because it is not emitted for every normal pull request.