Skip to content

Untrack a committed .pyc - #7

Merged
inth3shadows merged 1 commit into
mainfrom
chore/untrack-committed-pyc
Oct 14, 2026
Merged

inth3shadows merged 1 commit into
mainfrom
chore/untrack-committed-pyc

Conversation

@inth3shadows

@inth3shadows inth3shadows commented Oct 14, 2026 •

Copy link
Copy Markdown
Owner

assets/__pycache__/generate-waitlist.cpython-313.pyc was committed in 07af3db (colbymchenry#708). .gitignore:71 already ignores __pycache__/, and .gitignore:73 deliberately ignores its source, assets/generate-waitlist.py. The script was kept out of the repo, but its bytecode was committed anyway.

git rm --cached only. After: git ls-files -ci --exclude-standard prints nothing. The blob stays in history.

assets/__pycache__/generate-waitlist.cpython-313.pyc came in with colbymchenry#708.
.gitignore already ignores __pycache__/, so after this nothing re-adds it.
@inth3shadows
inth3shadows merged commit df030c6 into main Oct 14, 2026
inth3shadows added a commit that referenced this pull request Nov 6, 2026
Round-1 review of #16 found two regressions from the fork's new rules,
fixed in the fork (fa2be11, its PR #7):

- keyword tuple labels made `[type]`, `[get, set]`, `[declare?]` fail;
  labels are now only words that already lex as keywords where a type
  starts;
- `unique` as a reserved identifier broke `f<typeof unique>(x)`; backed
  out, so `i < unique.length` is a gap fixture again (VS Code's 2 files
  diverge, as on em.34).

New __tests__/typescript-grammar-fork-shapes.test.ts pins the node shapes
and the call edges (sql<Row>`...`, behind await, on a member; tuple labels;
typeof unique): 4 failed on 84ffdb8, 8 passed on fa2be11.

Docs: an operator before a typed tag (shared with generic calls), the
unique gap, `in?:`/`in<T>()` members, the Json5 line, a tag with 2+ type
args inside an argument list; the rebuild runs `tree-sitter test`; the
move checklist lists every vendored file, the hashes, and the marker
caveat. The fork commit is named once, in the grammar doc.

Differential: 201 -> 5 (effect 3, vscode 2), worse 0.
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.

1 participant