Skip to content

add workflow to copy doc issues to docs-content #557

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 22, 2021
Merged

Conversation

skedwards88
Copy link
Contributor

Following discussion between the docs team and API team, we decided to copy docs-related rest-api-description issues to the docs-content repo so that the issue can be triaged appropriately. (We create a copy instead of transferring so that the issue does not disappear for the contributor.)

This PR adds a workflow that will create a copy of an issue when the documentation label is added and comment on the new issue about where the issue came from, the priority, and what to do when resolving the issue.

Note: The workflow references a secret called PERSONAL_ACCESS_TOKEN. A PAT that the ability to read issues in the rest-api-description repo and write issues in the docs-content repo should be stored as a secret in the rest-api-description repo. The workflow should be updated to reference this new secret.

@imwiss imwiss merged commit 97aef4f into main Sep 22, 2021
@mmrobins mmrobins deleted the ske-copy-to-docs branch May 8, 2023 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants