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
feature: implemented @current and @next iteration selection (#45)
* feature: implemented @current and @next iteration selection
To use this functionality, simply pass @current or @next as the iteration value.
* tests: added @current and @next to the test cases
* docs: added instructions how to use the @current and @next iteration
Copy file name to clipboardExpand all lines: README.md
+23-5
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,7 @@ jobs:
151
151
To leverage the App authentication with this action the following steps are needed:
152
152
153
153
- Create a GitHub App under your user or organisation as described in the [GitHub documentation](https://docs.github.com/en/developers/apps/building-github-apps/creating-a-github-app), note the App ID
154
-
- Set the needed GitHub App permissions in order for the newly create App to access and manage Org Project, as described in the [GitHub documentation](https://docs.github.com/en/developers/apps/managing-github-apps/editing-a-github-apps-permissions). The minimum required permissions are:
154
+
- Set the needed GitHub App permissions in order for the newly create App to access and manage Org Project, as described in the [GitHub documentation](https://docs.github.com/en/developers/apps/managing-github-apps/editing-a-github-apps-permissions). The minimum required permissions are:
155
155
- Repo: Actions: RW
156
156
- Repo: Checks: RO
157
157
- Repo: Contents: RO
@@ -164,10 +164,9 @@ To leverage the App authentication with this action the following steps are need
164
164
- Create a private key to authenticate the newly created GitHub App as described in the [GitHub documentation](https://docs.github.com/en/developers/apps/building-github-apps/authenticating-with-github-apps), treat the downloaded key as sensitive material, store it in a GitHub secret accessible by this action.
165
165
- Install the app in the target organisation, note the installation ID
166
166
- Configure this action with
167
-
- `gh_app_secret_key` containing the aforementioned private key
168
-
- `gh_app_ID`containing the app ID, auto-generated by GitHub in the first step
169
-
- `gh_app_installation_ID`containing the installation ID, auto-generated by GitHub in the previous step. Binging the App to the Org
170
-
167
+
- `gh_app_secret_key` containing the aforementioned private key
168
+
- `gh_app_ID`containing the app ID, auto-generated by GitHub in the first step
169
+
- `gh_app_installation_ID`containing the installation ID, auto-generated by GitHub in the previous step. Binging the App to the Org
Since this repository is also covered by this automation, you can take a look at the definition within the [project-automation.yml](.github/workflows/project_automations.yml) file to check how it is defined here.
0 commit comments