auto-create new issue in documentation repo when needs-docs label in PR
#3363
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e in the documentation repository when a PR with a `needs-docs` label is merged in the main repository. This is intended to support improved documentation. Additional steps required 1. In order to work, the related PR in the documentation repository will also need to be merged, as it contains a job that actually creates the issue. The action in this repository simply triggers an alert and passes information to the other repository. 2. I have created a GitHub bot with the sole purpose of enabling the use of authorisation tokens with tightly-scoped permissions owned by the organization rather than an individual. We need this because we're triggering an action in one repository to do trigger another action in a different repository. Ownership has been transferred to `bookwyrm-social`. A new private key should be generated, and the `APPLICATION_ID` and `APPLICATION_PRIVATE_KEY` need to be added to the main repository's _Action_ `SECRETS`. Both repositories (or "All repositories") must be granted access, in the Bot configuration screen. 3. In the main repository settings, _Actions - General_ permissions must be set to _Allow all actions and reusable workflows_.
hughrun
added a commit
to hughrun/documentation
that referenced
this pull request
Apr 28, 2024
This is a sibling commit for bookwyrm-social/bookwyrm#3363 These add a pair of GitHub Actions to create a new issue in the documentation repository when a PR with a `needs-docs` label is merged in the main repository. 1. In order to work, the related PR in the main repository will also need to be merged, as it triggers the job here, and the Bot set up as described in the PR in the main repository.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds one of a pair of GitHub Actions to create a new issue in the documentation repository when a PR with a
needs-docslabel is merged in the main repository. This is intended to support improved documentation.Additional steps required
In order to work, the related PR in the documentation repository will also need to be merged, as it contains a job that actually creates the issue. The action in this repository simply triggers an alert and passes information to the other repository.
I have created a GitHub bot with the sole purpose of enabling the use of authorisation tokens with tightly-scoped permissions owned by the organization rather than an individual. We need this because we're triggering an action in one repository to do trigger another action in a different repository. Ownership will be transferred to
bookwyrm-socialassuming this PR is welcomed. A new private key needs to be generated, and theAPPLICATION_IDandAPPLICATION_PRIVATE_KEY(i.e.the key just generated) need to be added to the main repository's ActionSECRETS. Both repositories (or "All repositories") must be granted access, in the Bot configuration screen.In the main repository settings, Actions - General permissions must be set to Allow all actions and reusable workflows.