Repository navigation
Run the build and every check on each pull request (M1) - #31
Merged
Merged
Conversation
CI on every pull request and every push to main: a windows job builds src/Clayo Debug and Release with -warnaserror and runs every check. A newer push to the same branch cancels the run it replaces. scripts/checks.ps1 runs the checks in checks/, all of them or the ones named, and exits with the number that failed. A failing check prints its own output, so the log says which case broke. -Core runs only the checks that target net10.0 (none yet; M3 adds them). mascot.cs is left out: it renders PNGs to compare by eye, it isn't pass/fail. README gets a CI badge; CONTRIBUTING.md says how to build and check.
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.
Every pull request and every push to
mainnow builds Clayo and runs every check on GitHub. A red run shows which check broke and which case inside it failed.CI (
.github/workflows/ci.yml)windowsjob onwindows-latestbuildssrc/ClayoDebug and Release with-warnaserror, then runsscripts/checks.ps1.release.yml. The token is read-only.release.ymlis unchanged.scripts/checks.ps1checks/, or only the ones you name (.\scripts\checks.ps1 status sessions), and exits with the number that failed. It behaves the same locally and on CI.-Coreruns only the checks that targetnet10.0. There are none yet; they come with the Mac work (M3) and will also run on macOS.mascot.csis left out. It renders PNGs to compare by eye, it isn't a pass/fail check.Docs
CONTRIBUTING.md: branch, build,scripts/checks.ps1, PR.After merging
Make
windowsa required check onmainin the ruleset, only once this PR's run is green.Testing
dotnet buildanddotnet build -c Releasewith-warnaserrorgive 0 warnings and 0 errors.scripts/checks.ps1passes all 19 checks in about 45s. Named runs,-Coreand an unknown name behave as expected.