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
+40-19Lines changed: 40 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,39 +1,62 @@
1
-
# GitHub JavaScript action template
1
+
# bot
2
2
3
-
[](https://developersitalia.slack.com/messages/CAM3F785T)
The bot automating the [publiccodeyml organization](https://github.com/publiccodeyml/)
4
+
procedures implemented as a GitHub action.
5
5
6
-
This is a template repository for [creating a GitHub JavaScript action](https://docs.github.com/en/actions/creating-actions/creating-a-javascript-action).
6
+
## Commands
7
7
8
-
Click `Use this template` button to create your action based on this template.
8
+
The bot is instructed to perform tasks using its tag (fe. @yaml-9000) in issues
9
+
and PR comments followed by the command.
9
10
10
-
A sample action to get GitHub star counts and license from a given repository.
11
+
*`@yaml-9000 vote-start`: Open the pools for the voting procedure on the current
12
+
proposal
11
13
12
-
## Inputs
14
+
*`@yaml-9000 vote-end`: End the voting procedure, closing the pools and
15
+
announcing the results.
13
16
14
-
The following inputs briefly explained here are fully declared and documented in the [action.yaml](action.yaml):
17
+
*`@yaml-9000 breaking-change`: Mark the proposal as a [breaking change to the Standard](https://github.com/publiccodeyml/publiccode.yml/blob/main/governance/procedure-proposing-changes-and-voting.md#proposing-changes).
15
18
16
-
*`repo`[**Required**] - GitHub repository to fetch (default `${{ github.repository }}`)
19
+
Aliases: `breaking`, `major`
17
20
18
-
*`github_token`[**Optional**] - GitHub token to interact with GitHub API (default `${{ github.token }}`)
21
+
*`@yaml-9000 minor-change`: Mark the proposal as a [minor change to the Standard](https://github.com/publiccodeyml/publiccode.yml/blob/main/governance/procedure-proposing-changes-and-voting.md#proposing-changes)
22
+
23
+
Aliases: `minor`
24
+
25
+
*`@yaml-9000 bugfix-change`: Mark the proposal as a [bugfix change to the Standard](https://github.com/publiccodeyml/publiccode.yml/blob/main/governance/procedure-proposing-changes-and-voting.md#proposing-changes)
26
+
27
+
Aliases: `bugfix`, `patch`
28
+
29
+
*`@yaml-9000 national-section`: Mark the proposal as a [change in the national section](https://github.com/publiccodeyml/publiccode.yml/blob/main/governance/procedure-proposing-changes-and-voting.md#country-specific-sections) ([doc](https://yml.publiccode.tools/country.html))
This is now marked as a [`breaking-change` proposal to the standard](https://github.com/publiccodeyml/publiccode.yml/labels/standard-breaking-change) proposal to the Standard, this means that an old version of `publiccode.yml` won't be compatible with the new version.
4
+
5
+
Breaking changes can be released with a new major version at most once every two years, provided the current version of the Standard has been deprecating the object of this proposal for at least 6 months.
6
+
7
+
Example of breaking changes are removal of keys or changes to key types.
8
+
9
+
cc {{ chair_tag }} @{{{ steering_committee_team }}}
This is now marked as a [`deprecation-change` proposal to the standard](https://github.com/publiccodeyml/publiccode.yml/labels/standard-deprecation), this means that this change won't break any compatibility with the old versions of the Standard,
4
+
and it will be possibile to make the definitive change 6 months after the deprecation with a new major release.
5
+
6
+
cc {{ chair_tag }} @{{{ steering_committee_team }}}
0 commit comments