-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix(vscode): use shell mode for spawn on Windows to detect npm correctly #626
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
Changes from all commits
d7711c0
fa90a47
117959d
ffda357
f404e9b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,7 +2,7 @@ name: translation-sync | |
|
|
||
| # Content-validation guardrails, kept out of ci.yml (which is build/test/lint): | ||
| # - blocking: all README*.md translations share the same ## section structure. | ||
| # - non-blocking: warn when a docs/en page changes without its zh/ja/ru counterpart. | ||
| # - non-blocking: warn when a docs/en page changes without its zh/ja counterpart. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [documentation · medium] Either:
|
||
| # Scoped with paths: so it only runs when a translation or the checker changes, | ||
| # and a slow container pull here never delays core CI feedback. | ||
|
|
||
|
|
@@ -40,7 +40,7 @@ jobs: | |
| run: node scripts/github-actions/check-translation-sync.js readmes | ||
|
|
||
| # NON-BLOCKING: on PRs, warn (::warning) when a file under | ||
| # pages/src/content/docs/en/** changed without its zh/ja/ru counterpart. | ||
| # pages/src/content/docs/en/** changed without its zh/ja counterpart. | ||
| # continue-on-error keeps it advisory: it never fails the build. | ||
| # The event_name guard is intentional even though on: is PR-only today: | ||
| # if a push: trigger is reintroduced, base/head.sha would be empty. | ||
|
|
||
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 · medium]
Third-party actions should be pinned to a full commit SHA rather than a mutable tag. Tags can be moved or hijacked, posing a supply-chain risk. Consider pinning to the specific commit SHA for
softprops/action-gh-release@v2(e.g.,uses: softprops/action-gh-release@<full-sha>). First-partyactions/*pinned to major version tags like@v4/@v2are acceptable.