You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-37Lines changed: 1 addition & 37 deletions
Original file line number
Diff line number
Diff line change
@@ -38,40 +38,4 @@ build:
38
38
1) implement your changes
39
39
2) commit changes (pre-commit hook will do some code checks / changes and build the artifacts using ncc)
40
40
3) set tag `git tag -a -m "my fancy release" v0.0.X`
41
-
4) push with tags `git push --follow-tags`
42
-
43
-
## Publish to a distribution branch
44
-
45
-
Actions will be consumed from GitHub repos. All the dependencies must be pushed there. This means for JS also
46
-
`node_module`must be published.
47
-
48
-
Comment out `node_modules` in [.gitignore](./.gitignore) and create a `releases/**` branch
49
-
```bash
50
-
# comment out in distribution branches
51
-
# node_modules/
52
-
```
53
-
54
-
Then run the following commands:
55
-
56
-
```bash
57
-
$ git checkout -b releases/v1
58
-
$ npm prune --production
59
-
$ git add node_modules
60
-
$ git commit -a -m "prod dependencies"
61
-
$ git push origin releases/v1
62
-
```
63
-
64
-
Your action is now published! :rocket:
65
-
66
-
See the [versioning documentation](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md)
67
-
68
-
## Usage:
69
-
70
-
After testing you can [create a v1 tag](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md) to reference the stable and tested action
0 commit comments