add workflow to copy doc issues to docs-content #557
Merged
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.
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 therest-api-description
repo and write issues in thedocs-content
repo should be stored as a secret in therest-api-description
repo. The workflow should be updated to reference this new secret.