The fork does not use the VSCode extension. The CI install also failed,
because the extension ran tsx from a prepare script and never
declared tsx as a dependency.
Remove both integrations/vscode packages, the release-vsix workflow,
the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
Description
Linked Issues
Additional Context
The fork does not use the VSCode extension. The CI install also failed,
because the extension ran `tsx` from a `prepare` script and never
declared `tsx` as a dependency.
Remove both `integrations/vscode` packages, the release-vsix workflow,
the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
## Description
<!-- Please insert your description here and especially provide info about the "what" this PR is solving -->
## Linked Issues
<!-- Optional, if you have any -->
## Additional Context
<!-- e.g. is there anything you'd like reviewers to focus on? -->
The fork does not use the VSCode extension. The CI install also failed,
because the extension ran `tsx` from a `prepare` script and never
declared `tsx` as a dependency.
Remove both `integrations/vscode` packages, the release-vsix workflow,
the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
The fork does not run CI on github.com. The autofix.ci GitHub App is the
only service that can read the patch artifact and open the fix commit,
so every run failed at the artifact upload: local `act` runs have no
artifact server, and self-hosted hosts have no autofix.ci App.
Every job installed the full workspace on each run. Cache the Bun global
cache and key it on bun.lock, so a run only downloads the packages that
the lockfile changed.
actions/setup-node cannot do this, because its cache input supports npm,
yarn, and pnpm only.
Some checks are pending
CI / Build Test (stage-web) (pull_request) Waiting to run
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The fork does not use the VSCode extension. The CI install also failed,
because the extension ran
tsxfrom apreparescript and neverdeclared
tsxas a dependency.Remove both
integrations/vscodepackages, the release-vsix workflow,the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
Description
Linked Issues
Additional Context
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.