bookwyrm/.github/workflows
Hugh Rundle ea15dabfc4
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-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_.
2024-04-28 14:00:03 +10:00
..
codeql-analysis.yml Update CodeQL workflows to v3 2024-03-30 21:56:44 +01:00
curlylint.yaml CI: use actions/checkout@v4 2024-03-13 23:33:40 +01:00
lint-frontend.yaml Install same version of eslint in CI as in dev-tools 2024-04-10 21:26:34 +02:00
prettier.yaml CI: use actions/checkout@v4 2024-03-13 23:33:40 +01:00
python.yml CI: relax black version constraints 2024-03-20 12:46:37 +01:00
trigger_docs_issue.yml 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-docs label is merged in the main repository. This is intended to support improved documentation. 2024-04-28 14:00:03 +10:00