Repository navigation
Build the @moq packages from a moq submodule #198
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
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| [submodule "moq"] | ||
| path = moq | ||
| url = https://github.com/moq-dev/moq |
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -44,9 +44,12 @@ With [direnv](https://direnv.net/) installed, `direnv allow` loads that shell | |
| automatically on every `cd` into the repo. | ||
|
|
||
| Don't have Nix? Install `bun`, Node.js 24, and `just` yourself, matching the `bun` | ||
| version in `packageManager`. Either way, the dependencies come from `bun`: | ||
| version in `packageManager`. You still need `nix` on your `PATH`: the `@moq/*` | ||
| packages build from the `moq` submodule, and its `@moq/libav` is built with Nix. | ||
| Either way, fetch the submodule and install with `bun`: | ||
|
|
||
| ```bash | ||
| git submodule update --init | ||
|
Comment on lines
+49
to
+52
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. 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win Initialize the submodule before the first setup command. On a fresh clone without submodules, the earlier 🤖 Prompt for AI Agents
|
||
| bun i | ||
| ``` | ||
|
|
||
|
|
||
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 | 🟡 Minor | ⚡ Quick win
Restrict the GitHub token before running checked-out code.
The
checkjob runsbun install,bun run check, andbun testafter checkout. It has nopermissionsblock, soGITHUB_TOKENinherits repository defaults.actions/checkoutalso persists the token in local Git configuration. Checked-out code can read the token. Addpermissions: contents: readtocheckand setpersist-credentials: falseon the checkout steps.🧰 Tools
🪛 zizmor (1.30.1)
[warning] 12-16: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
[warning] 1-46: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
[warning] 8-33: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
🤖 Prompt for AI Agents
Source: Linters/SAST tools