ci: Add workflow to automate API reference sync on new version tags #822
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.
Automation
The API reference generated in this repository is published via the
docsrepository for the project. This means that we regularly need to synchronize the document.Instead of manually copying the API reference and creating a new Pull Request in the
docsrepo, let's add a workflow to automate this task. The workflow runs each time a new version tag is created in thefabricrepository.Test
The workflow was tested successfully between my own forks of the
fabricanddocsrepositories, leading to the automated creation of qmonnet/hhdocs#1 when I pushed a tag to my fork.Authentication
For my test I used a fine-grained PAT (using the scope from the docs), passed as a repository secret. For the upstream
fabricrepo we probably need something different, something that makes thegithub-actionsbot the author of the PR, maybe a GitHub App token? I'm not familiar with using those, though.