|
1 | | -<p align="center"> |
2 | | - <a href="https://github.com/actions/typescript-action/actions"><img alt="typescript-action status" src="https://github.com/actions/typescript-action/workflows/build-test/badge.svg"></a> |
3 | | -</p> |
| 1 | +# calvinallen/action-vs-vsix-versioner |
4 | 2 |
|
5 | | -# Create a JavaScript Action using TypeScript |
| 3 | +Github Action to update your Visual Studio extension to a version that is based off of the current date and the CI build number. |
6 | 4 |
|
7 | | -Use this template to bootstrap the creation of a TypeScript action.:rocket: |
| 5 | +> *This action requires your extension to utilize the [VSIX Synchronizer](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.VsixSynchronizer64) model for managing the version in the `source.extension.vsixmanifest` and the `source.extension.cs` code-behind file that is automatically synchronized.* |
| 6 | +> |
| 7 | +> *Other versioning styles will be supported in the future* |
8 | 8 |
|
9 | | -This template includes compilation support, tests, a validation workflow, publishing, and versioning guidance. |
| 9 | +## Usage |
10 | 10 |
|
11 | | -If you are new, there's also a simpler introduction. See the [Hello World JavaScript Action](https://github.com/actions/hello-world-javascript-action) |
| 11 | +You can use the Visual Studio VSIX Versioner GitHub Action by configuring a YAML-based workflow file, e.g. .github/workflows/deploy.yml. |
12 | 12 |
|
13 | | -## Create an action from this template |
| 13 | +> *This action only works on a Windows-based runner* |
14 | 14 |
|
15 | | -Click the `Use this Template` and provide the new repo details for your action |
| 15 | +## Version the VSIX *befre* building |
16 | 16 |
|
17 | | -## Code in Main |
| 17 | +```yml |
| 18 | +steps: |
| 19 | + - name: Checkout |
| 20 | + uses: actions/checkout@v2 |
18 | 21 |
|
19 | | -> First, you'll need to have a reasonably modern version of `node` handy. This won't work with versions older than 9, for instance. |
| 22 | + - name: Visual Studio VSIX Versioner |
| 23 | + uses: CalvinAllen/action-vs-vsix-versioner@v1 |
| 24 | + with: |
| 25 | + # REQUIRED |
| 26 | + extension-manifest-file: './src/CodingWithCalvin.OpenBinFolder.Vsix/source.extension.vsixmanifest' |
| 27 | + extension-source-file: './src/CodingWithCalvin.OpenBinFolder.Vsix/source.extension.cs' |
20 | 28 |
|
21 | | -Install the dependencies |
22 | | -```bash |
23 | | -$ npm install |
24 | | -``` |
25 | | - |
26 | | -Build the typescript and package it for distribution |
27 | | -```bash |
28 | | -$ npm run build && npm run package |
29 | | -``` |
30 | | - |
31 | | -Run the tests :heavy_check_mark: |
32 | | -```bash |
33 | | -$ npm test |
34 | | - |
35 | | - PASS ./index.test.js |
36 | | - ✓ throws invalid number (3ms) |
37 | | - ✓ wait 500 ms (504ms) |
38 | | - ✓ test runs (95ms) |
39 | | - |
40 | | -... |
41 | | -``` |
42 | | - |
43 | | -## Change action.yml |
44 | | - |
45 | | -The action.yml defines the inputs and output for your action. |
46 | | - |
47 | | -Update the action.yml with your name, description, inputs and outputs for your action. |
48 | | - |
49 | | -See the [documentation](https://help.github.com/en/articles/metadata-syntax-for-github-actions) |
50 | | - |
51 | | -## Change the Code |
52 | | - |
53 | | -Most toolkit and CI/CD operations involve async operations so the action is run in an async function. |
54 | | - |
55 | | -```javascript |
56 | | -import * as core from '@actions/core'; |
57 | | -... |
| 29 | + # OPTIONAL |
| 30 | + build-number: ${{ github.run_number }} |
58 | 31 |
|
59 | | -async function run() { |
60 | | - try { |
61 | | - ... |
62 | | - } |
63 | | - catch (error) { |
64 | | - core.setFailed(error.message); |
65 | | - } |
66 | | -} |
67 | 32 |
|
68 | | -run() |
69 | 33 | ``` |
70 | 34 |
|
71 | | -See the [toolkit documentation](https://github.com/actions/toolkit/blob/master/README.md#packages) for the various packages. |
72 | | - |
73 | | -## Publish to a distribution branch |
74 | | - |
75 | | -Actions are run from GitHub repos so we will checkin the packed dist folder. |
76 | | - |
77 | | -Then run [ncc](https://github.com/zeit/ncc) and push the results: |
78 | | -```bash |
79 | | -$ npm run package |
80 | | -$ git add dist |
81 | | -$ git commit -a -m "prod dependencies" |
82 | | -$ git push origin releases/v1 |
83 | | -``` |
84 | | - |
85 | | -Note: We recommend using the `--license` option for ncc, which will create a license file for all of the production node modules used in your project. |
86 | | - |
87 | | -Your action is now published! :rocket: |
88 | | - |
89 | | -See the [versioning documentation](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md) |
90 | | - |
91 | | -## Validate |
92 | | - |
93 | | -You can now validate the action by referencing `./` in a workflow in your repo (see [test.yml](.github/workflows/test.yml)) |
94 | | - |
95 | | -```yaml |
96 | | -uses: ./ |
97 | | -with: |
98 | | - milliseconds: 1000 |
99 | | -``` |
100 | | -
|
101 | | -See the [actions tab](https://github.com/actions/typescript-action/actions) for runs of this action! :rocket: |
102 | | -
|
103 | | -## Usage: |
| 35 | +## Inputs |
104 | 36 |
|
105 | | -After testing you can [create a v1 tag](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md) to reference the stable and latest V1 action |
| 37 | +| Input | Required | Description | |
| 38 | +| ------------------------ | -------- | -------------------------------------------------------------------------------------------------------------------- | |
| 39 | +| extension-manifest-file | Y | Path to the manifest used for the extension | |
| 40 | +| extension-source-file | Y | Path to the source file generated from the manifest (using VSIX Syncronizer) | |
| 41 | +| build-number | N | Specify the build number you'd like to utilize, otherwise, defaults to the `run_number` of the build itself | |
0 commit comments