zotero-plugin 1.3.0 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -3,14 +3,14 @@
|
|
|
3
3
|
Utility scripts for releasing zotero plugins on github. See also https://github.com/retorquere/generator-zotero-plugin/
|
|
4
4
|
|
|
5
5
|
zotero-plugin-release will release your plugin as a github release.
|
|
6
|
-
When it is ran on master/main, and it detects a tagged build
|
|
6
|
+
When it is ran on master/main, and it detects a tagged build in a Github Action,
|
|
7
7
|
it will issue a new release. When it is ran on a branch named
|
|
8
8
|
`gh-<number>`, it will publish the plugin to a pre-release named
|
|
9
9
|
`builds`, and will announce the new build on issue number `<number>`
|
|
10
10
|
in your repo.
|
|
11
11
|
|
|
12
12
|
For this to work you must have a variable named `GITHUB_TOKEN` in
|
|
13
|
-
your
|
|
13
|
+
your GH Actions environment with a github token with `repo` rights. You
|
|
14
14
|
are allowed one bot account by github; I use this to do the
|
|
15
15
|
announcements, but you can use one from your own account if you
|
|
16
16
|
want.
|