coder/code-server
1
1
Fork 0
mirror of https://github.com/coder/code-server.git synced 2024-12-01 13:47:28 +03:00
Code Issues Packages Projects Releases Wiki Activity
fc6064dcd3
code-server/.prettierignore

11 lines
165 B
Plaintext
Raw Normal View History

refactor: update prettier and doctoc (#5605) * docs: add toc to CODE OF CONDUCT * chore: add prettier ignore blocks to docs * chore: update styles for Dockerfile * refactor: separate prettier, doctoc This does a couple things: - update `.prettierignore` - split `prettier` and `doctoc` commands. you can still run with `yarn fmt` - delete `fmt.sh` and add `doctoc.sh` By doing so, we can run tasks in parallel in CI and we should also have less false positives than before with `yarn fmt` locally. * refactor: update prettier job, add doctoc This modifies the prettier job to use actionsx/prettier. It also adds a job for `doctoc`. * chore: upgrade to prettier 2.7.1 * chore: pin doctoc to 2.0.0 * fixup!: add .pc to prettierignore * feat: add --cache to prettier cmd
2022-10-14 01:16:55 +03:00
lib/vscode
chore: prettierignore updates and setup-helm upgrade (#5721) * chore: update prettierignore * chore: upgrade setup-helm 3.4
2022-10-28 19:15:19 +03:00
lib/vscode-reh-web-linux-x64
release-standalone
release: 4.9.0 (#5772) * wip: changelog * fixup * fix: add +x to product.json in build-vscode While testing a pre-release, there seems to be a bug with the file permissions for `product.json`. Adding `chmod +x` to see if that fixes it. * chore: increase timeout * fix: keep product.json file permissions in release When we added the change to modify the `package.json` version using `mv` and `jq` we didn't account for lost file permissions. This caused a bug only happening in CI. This should fix it by giving it 755 via `chmod`. * trigger ci * chore: update package.json bust cache * fixup!: fix: keep product.json file permissions in release * Revert "fix: add +x to product.json in build-vscode" This reverts commit fc4d2b532f41277d6b93243cd6bd2ba2434f80d6. * chore: pin ubuntu runner in build code-server * chore: update prettierignore * chore: add notes to changelog * chore: use ubuntu-22.04 for e2e * chore: pin all jobs in build to ubuntu 20.04 * feat(wrapper): add tests for isChild * fixup: include description ts-expect-error comment * chore: update CHANGELOG * chore: update Helm chart * fixup: use our childProcess * Update CHANGELOG.md Co-authored-by: Asher <ash@coder.com> Co-authored-by: Asher <ash@coder.com>
2022-12-06 23:28:27 +03:00
release-packages
chore: prettierignore updates and setup-helm upgrade (#5721) * chore: update prettierignore * chore: upgrade setup-helm 3.4
2022-10-28 19:15:19 +03:00
release
refactor: update prettier and doctoc (#5605) * docs: add toc to CODE OF CONDUCT * chore: add prettier ignore blocks to docs * chore: update styles for Dockerfile * refactor: separate prettier, doctoc This does a couple things: - update `.prettierignore` - split `prettier` and `doctoc` commands. you can still run with `yarn fmt` - delete `fmt.sh` and add `doctoc.sh` By doing so, we can run tasks in parallel in CI and we should also have less false positives than before with `yarn fmt` locally. * refactor: update prettier job, add doctoc This modifies the prettier job to use actionsx/prettier. It also adds a job for `doctoc`. * chore: upgrade to prettier 2.7.1 * chore: pin doctoc to 2.0.0 * fixup!: add .pc to prettierignore * feat: add --cache to prettier cmd
2022-10-14 01:16:55 +03:00
helm-chart
test/scripts
test/e2e/extensions/test-extension
.pc
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 07:31:28 +03:00
package-lock.json
Reference in New Issue Copy Permalink