Jason Fields
bd73840b51
Upgrade node to v18
2023-10-19 00:01:29 -04:00
Jason Fields
2048b59ccd
Try caching node packages in GitHub Actions
2023-04-05 17:03:58 -04:00
Jason Fields
af8052c119
Update setup-node GitHub Action to v3
2023-03-11 16:27:25 -05:00
Jason Fields
c7e237ad88
Add lint and lint:fix scripts
2023-03-01 20:29:42 -05:00
Jason Fields
56b77ba6d0
Use prettier CLI instead of GitHub Action
2023-03-01 20:21:23 -05:00
Jason Fields
d94f2b59e2
Use node v16 on GitHub Actions
2022-12-05 19:36:07 -05:00
Jason Fields
c89e8e1aa1
Add yarn package script
2022-04-07 01:24:38 -04:00
Jason Fields
09e28d4088
Only run CI on PRs and the master branch
...
Renovate PRs currently run CI twice on each platform, which is just wasteful
2022-03-11 17:23:56 -05:00
Filip Troníček
bd66226c7d
Automatically publish extension to OpenVSX ( #7527 )
...
Fixes #7183
2022-03-08 13:57:19 -05:00
WhiteSource Renovate
e794fcb6a4
Update actions/checkout action to v3 ( #7539 )
2022-03-01 23:57:16 -05:00
Jason Fields
9718f5b0df
ANOTHER attempt at getting prettier to work via GHA
...
I've given up; for now, just make the action fail if something is badly formatted, rather than fixing it automatically.
2022-01-31 16:54:36 -05:00
Jason Fields
24abb7016a
Another attempt at fixing prettier GitHub Action
2022-01-31 15:08:35 -05:00
Jason Fields
cc3ee3c873
Fix prettier GitHub Action... maybe?
2022-01-28 23:40:14 -05:00
J.R. Maingat
b7fd095ed2
Silence failing tests on Windows and add Windows build step ( #7293 )
...
Refs #4844 , refs #4079
2022-01-25 23:18:04 -05:00
Jason Fields
7a24104d57
Use node v14 in GitHub Actions
2021-11-04 13:50:47 -04:00
Jason Fields
0e4e49039f
Remove --web flag from vsce
...
This was removed in 1.94 (5b79e01717
2021-07-02 16:43:31 -04:00
WhiteSource Renovate
5d5c8dcecd
Update creyD/prettier_action action to v3.3 ( #5981 )
2021-01-11 13:00:35 -05:00
Jason Fields
d01f5dc16e
Only prettify changed files in CI
2020-12-17 11:39:35 -05:00
Jason Fields
1897cb13ef
Run 'build' CI action only on branches and PRS, not tags
...
Tags are used for releases and they do the same build/lint/test in their own job. No need to do it twice.
There's probably a way of refactoring this stuff out, but our CI configuration is simple enough that I don't really care at the moment.
2020-12-08 14:33:43 -05:00
rebornix
690ddae8f7
update vsce publish to support web bits.
2020-12-07 08:25:45 -08:00
Jason Fields
e8693fc4eb
Actually fix release workflow
2020-12-06 16:48:13 -05:00
Jason Fields
d824950a71
Fix release workflow
2020-12-06 16:27:51 -05:00
Jason Fields
0cd3ac6cb2
Create release workflow for GitHub Actions
2020-12-06 15:51:13 -05:00
Jason Fields
de29e73153
Use yarn instead of npm
...
We've had a yarn.lock alongside package-lock.json for a while now, and there should really only be one.
Yarn is faster and more deterministic, and while it's one more download, it's almost entirely a drop-in replacement for npm.
There is Yarn 2.x (also known as Berry for some reason), but from what I've read, it requires a more substantial migration and is more controversial. Let's stay on 1.x for now, and I'll look into upgrading at some point down the line.
2020-12-06 15:37:10 -05:00
Jason Fields
2296802a40
Change CI badge to reference GitHub Actions workflow
2020-12-06 13:34:27 -05:00
Jason Fields
23067308ec
Migrate from Travis CI to GitHub Actions
...
This only covers normal CI; I haven't yet set up releasing via GitHub Actions.
I've removed husky & pretty-quick because the CI will now run prettier and amend your commit, so they are redundant.
Fixes #5720
2020-11-20 19:46:23 -05:00
