Skip to content

Fix typos in CONTRIBUTING - #3753

Merged
wraithgar merged 1 commit into
npm:release-nextfrom
shadowspawn:feature/fix-typo
Sep 14, 2021
Merged

wraithgar merged 1 commit into
npm:release-nextfrom
shadowspawn:feature/fix-typo

Conversation

@shadowspawn

Copy link
Copy Markdown
Contributor

I was reading the CONTRIBUTING guidelines and noticed a couple of spelling errors (from a recent change).

@shadowspawn
shadowspawn requested a review from a team as a code owner September 14, 2021 06:01
@wraithgar
wraithgar changed the base branch from latest to release-next September 14, 2021 15:50
@wraithgar
wraithgar merged commit 291d977 into npm:release-next Sep 14, 2021
strvmarv added a commit to strvmarv/total-recall that referenced this pull request Apr 9, 2026
…-y @strvmarv/total-recall'

Ports the fix that exists on main but never made it into rewrite/dotnet.
The 'npx -y @strvmarv/total-recall' invocation trips the known npm
scoped-bin bug (npm/cli#3753): npx looks up
a bin matching the package scope rather than the 'bin' field in
package.json, so the command silently fails to resolve. The bare
'total-recall' form assumes a global npm install put the binary on
PATH, which is how every other host-specific plugin.json in this repo
(Cursor, Copilot, etc.) invokes it.

Discovered while auditing 'rewrite/dotnet' against 'main' ahead of the
post-cutover fast-forward. The 23 commits on main that aren't on
rewrite/dotnet are otherwise fully reflected in rewrite/dotnet's tree
(TOTAL_RECALL_DB_PATH feature ported, skill rename ported, hooks
host-agnostic refactor ported, hooks/ byte-identical). This is the one
content drift that needed a real port.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants