Move release and PR creation to GitHub Actions #50
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.
In scope of this PR we've moved release and PR creation from AzureDevOps to GitHub Actions.
Details:
The main goal of these changes is to switch the repository to use the system account to publish Python releases and create PRs with updating the
versions-manifest.json
file. For this purpose we useGITHUB_TOKEN
which is automatically generated by GitHub. Unfortunately, we were not able to get rid of the personal access token completely. We have to authenticate using a personal access token to trigger workflow configured with theworkflow_dispatch
andrepository_dispatch
events.We cannot completely move python-versions CI to the GitHub Actions because we have to use
macOS-10.14
pool to build our packages. We will move to GitHub Actions as soon as possible.