Skip to content

Commit 7ba38da

Browse files
authored
Merge pull request #8 from VSCodeVim/master
update master
2 parents c659655 + 8c08b9c commit 7ba38da

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

76 files changed

+2084
-11082
lines changed

.github/CONTRIBUTING.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ When submitting a PR, please fill out the template that is presented by GitHub w
2626
1. Install prerequisites:
2727
- latest [Visual Studio Code](https://code.visualstudio.com/)
2828
- [Node.js](https://nodejs.org/) v12.0.0 or higher
29+
- [Yarn](https://classic.yarnpkg.com/) v1.x
2930
- _Optional_: [Docker Community Edition](https://store.docker.com/search?type=edition&offering=community) 🐋
3031
1. In a terminal:
3132

@@ -35,7 +36,7 @@ When submitting a PR, please fill out the template that is presented by GitHub w
3536
cd Vim
3637

3738
# Install the dependencies
38-
npm install
39+
yarn install
3940

4041
# Open in VSCode
4142
code .
@@ -46,7 +47,7 @@ When submitting a PR, please fill out the template that is presented by GitHub w
4647

4748
# Alternatively, build and run tests through gulp and npm scripts
4849
npx gulp build # build
49-
npm test # test (must close all instances of VSCode)
50+
yarn test # test (must close all instances of VSCode)
5051

5152
# Only available if Docker is installed and running
5253
npx gulp test # run tests inside Docker container
@@ -110,7 +111,7 @@ In addition to building and testing the extension, when a tag is applied to the
110111
111112
### Visual Studio Code Slowdown
112113
113-
If you notice a slowdown and have ever run `npm test` in the past instead of running tests through VSCode, you might find a `.vscode-test/` folder, which VSCode is continually consuming CPU cycles to index. Long story short, you can speed up VSCode by:
114+
If you notice a slowdown and have ever run `yarn test` in the past instead of running tests through VSCode, you might find a `.vscode-test/` folder, which VSCode is continually consuming CPU cycles to index. Long story short, you can speed up VSCode by:
114115
115116
```bash
116117
$ rm -rf .vscode-test/

.github/workflows/build.yml

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
name: build
2+
3+
on:
4+
push:
5+
branches:
6+
- '**'
7+
pull_request:
8+
branches:
9+
- '**'
10+
11+
jobs:
12+
build:
13+
runs-on: ubuntu-latest
14+
steps:
15+
- name: Checkout VSCodeVim
16+
uses: actions/checkout@v2
17+
with:
18+
# Get full history; needed for Prettier to amend commit
19+
fetch-depth: 0
20+
21+
- name: Set up Node.js
22+
uses: actions/setup-node@v2-beta
23+
with:
24+
node-version: '12'
25+
26+
- name: Install dependencies
27+
run: yarn install
28+
29+
- name: Prettier
30+
uses: creyD/prettier_action@v3.1
31+
with:
32+
prettier_options: '--write **/*.{ts,js,json,md,yml}'
33+
same_commit: true
34+
# TODO: enable this once https://github.com/creyD/prettier_action/issues/31 is fixed
35+
# only_changed: true
36+
env:
37+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
38+
39+
- name: Lint
40+
run: npx tslint -c tslint.json -p tsconfig.json
41+
42+
- name: Build
43+
run: gulp webpack
44+
45+
- name: Test
46+
run: |
47+
gulp prepare-test
48+
xvfb-run -a yarn test

.github/workflows/release.yml

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
name: Release
2+
3+
on:
4+
push:
5+
tags:
6+
- v1.[0-9]+.[0-9]+
7+
8+
jobs:
9+
release:
10+
runs-on: ubuntu-latest
11+
steps:
12+
- name: Checkout VSCodeVim
13+
uses: actions/checkout@v2
14+
15+
- name: Set up Node.js
16+
uses: actions/setup-node@v2-beta
17+
with:
18+
node-version: '12'
19+
20+
- name: Install dependencies
21+
run: yarn install
22+
23+
- name: Lint
24+
run: npx tslint -c tslint.json -p tsconfig.json
25+
26+
- name: Build
27+
run: gulp webpack
28+
29+
- name: Test
30+
run: |
31+
gulp prepare-test
32+
xvfb-run -a yarn test
33+
34+
- name: Build extension package
35+
id: build_vsix
36+
run: |
37+
yarn run vsce package --web;
38+
echo ::set-output name=vsix_path::$(ls *.vsix);
39+
40+
- name: Create release on GitHub
41+
id: create_release
42+
uses: actions/create-release@v1
43+
env:
44+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
45+
with:
46+
tag_name: ${{ github.ref }}
47+
release_name: ${{ github.ref }}
48+
draft: false
49+
prerelease: false
50+
51+
- name: Upload .vsix as release asset to GitHub
52+
uses: actions/upload-release-asset@v1
53+
env:
54+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
55+
with:
56+
upload_url: ${{ steps.create_release.outputs.upload_url }}
57+
asset_path: ${{ steps.build_vsix.outputs.vsix_path }}
58+
asset_name: ${{ steps.build_vsix.outputs.vsix_path }}
59+
asset_content_type: application/zip
60+
61+
- name: Publish to VSCode Extension Marketplace
62+
run: yarn run vsce publish --yarn --web
63+
env:
64+
VSCE_PAT: ${{ secrets.VSCE_PAT }}

.github_changelog_generator

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,6 @@ bugs-label=**Fixed Bugs:**
55
bug-labels=kind/bug
66
enhancement-label=**Enhancements:**
77
enhancement-labels=kind/enhancement,kind/feature
8-
exclude-labels=status/by-design,status/duplicate,kind/question,kind/discussion,pr/dependency
8+
exclude-labels=status/by-design,status/duplicate,status/user-error,status/already-resolved,kind/question,kind/discussion,pr/dependency,upstream/different-plugin,upstream/vscode
99
since-tag=v1.16.0
1010
max-issues=500

.travis.yml

Lines changed: 0 additions & 86 deletions
This file was deleted.

0 commit comments

Comments
 (0)