-
Notifications
You must be signed in to change notification settings - Fork 0
Add a Windows CI job covering lint, compile, and test (#518) #562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
leynos
wants to merge
23
commits into
main
Choose a base branch
from
issue-518-add-a-windows-ci-job-covering-lint-compile-and-test
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
0da08f0
ci: add non-blocking Windows build-test job
leynos 0ddd2a0
fix: gate which env capture chain for Windows production path
leynos c1d0d9a
fix: gate test_support items unused on Windows
leynos f9f97c0
fix: clear Windows-only Clippy and test-build findings
leynos eabcfbe
docs: record Windows CI job and PATHEXT cfg widening decision
leynos 104b4b1
fix: own the basename in windows workspace candidate collection
leynos b0c6248
fix: gate fixture import and use method reference in windows basenames
leynos f1f0729
ci: make Windows build-test job a blocking merge gate
leynos 32db2e1
fix: clear Windows-only Clippy and dead-code findings surfaced by blo…
leynos e48ae06
fix: gate Unix-only runner tests and ungate platform-independent glob…
leynos ab52b09
fix: clear Windows-only clippy findings in test helper stubs
leynos e070906
fix: clear Windows-only clippy findings in std_filter_tests
leynos 0972313
style: rustfmt the gated anyhow import in path_filters
leynos 8666eca
fix: clear next layer of Windows-only findings
leynos 4349fda
ci: shim whitaker for Git Bash on the Windows job
leynos 383d2dc
fix: route Windows grep-stream test through test_support::fs
leynos 5c4110c
fix: canonicalise discovery paths with dunce on Windows
leynos 27d4205
build: add dunce to build-dependencies
leynos 1ad8b04
Revert "build: add dunce to build-dependencies"
leynos ef3a7b4
Revert "fix: canonicalise discovery paths with dunce on Windows"
leynos eb642c2
ci: do not persist credentials on the Windows checkout step
leynos 676d7e1
ci: hoist NEXTEST_VERSION to workflow scope so the documented sed ext…
leynos 7352c2a
test: add behavioural workflow-contract tests for the Windows CI job
leynos File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
Does actions/checkout v7 persist the GitHub Actions token in local Git configuration by default, and does persist-credentials: false disable this?💡 Result:
Yes, by default, actions/checkout (including version 7) persists the GitHub Actions token in the local Git configuration [1][2][3]. Specifically, the action configures the token (or SSH key) in the local repository's
.git/configfile, which allows subsequent steps in the workflow to execute authenticated Git commands without needing to manually re-configure credentials [1][4][5]. Settingpersist-credentials: falseeffectively disables this behavior [1][2][5]. When this option is set to false, the action will not configure the token in the local Git configuration, thereby preventing subsequent steps from automatically using the checkout token for Git operations [5]. The token is also automatically removed during the post-job cleanup process when the default behavior is used [1][2][6].Citations:
🏁 Script executed:
Repository: leynos/netsuke
Length of output: 9126
Disable persisted checkout credentials.
Set
persist-credentials: falsefor the Windows checkout. Latermakecommands execute checked-out code that could read the read-scoped workflow token from local Git configuration.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 153-153: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
🤖 Prompt for AI Agents
Source: Linters/SAST tools
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@coderabbitai Has this now been resolved in the latest commit?
Use codegraph analysis to determine your answer.
If this comment is now resolved, please mark it as such using the API. Otherwise, please provide an AI agent prompt for the remaining work to be done to address this comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 4030
@leynos, the finding remains open.The latest revision,
b8c1e99aa1367ff03210b324267af9955e564ade, does not setpersist-credentials: falsefor thebuild-test-windowscheckout at Line 151. The job then runs repository-controlledmakecommands. The existingkani-smokecheckout shows the required configuration at Line 225.Use this AI agent prompt:
You are interacting with an AI system.