In scope of this PR we've moved node-versions CI from AzureDevOps to GitHub Actions
Details:
The main goal of these changes is to switch the repository to use the system account to publish Node.js releases and create PRs with updating the versions-manifest.json file. For this purpose we use GITHUB_TOKEN which is automatically generated by GitHub. Example of PR created using a system account:
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 the workflow_dispatch event.
GitHub Actions CI approach:
We've configured two workflows:
build-node-packages.yml - to build, test and publish Node.js packages
create-pr.yml - to create PRs with updating the versions-manifest.json file
All workflows are configured using the workflow_dispatch event and can be started manually, for example:
We did not move get-node-versions pipeline, it is still on the AzureDevOps
In scope of this PR we've moved node-versions CI from AzureDevOps to GitHub Actions
**Details:**
The main goal of these changes is to switch the repository to use the system account to publish Node.js releases and create PRs with updating the `versions-manifest.json` file. For this purpose we use `GITHUB_TOKEN` which is automatically generated by GitHub. Example of PR created using a system account:
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 the `workflow_dispatch` event.
**GitHub Actions CI approach:**
We've configured two workflows:
- `build-node-packages.yml` - to build, test and publish Node.js packages
- `create-pr.yml` - to create PRs with updating the `versions-manifest.json` file
All workflows are configured using the `workflow_dispatch` event and can be started manually, for example:
We did not move `get-node-versions` pipeline, it is still on the [AzureDevOps](https://github.visualstudio.com/virtual-environments/_build?definitionId=78)
dmitry-shibanov
(Migrated from github.com)
reviewed 2020-08-25 16:22:24 +05:00
miketimofeev
(Migrated from github.com)
reviewed 2020-08-25 16:22:24 +05:00
dibir-magomedsaygitov
(Migrated from github.com)
reviewed 2020-08-25 16:22:24 +05:00
maxim-lobanov
(Migrated from github.com)
approved these changes 2020-08-25 16:25:31 +05:00
vmapetr
(Migrated from github.com)
approved these changes 2020-08-25 16:27:55 +05:00
al-cheb
(Migrated from github.com)
approved these changes 2020-08-25 16:33:41 +05:00
nikita-bykov
(Migrated from github.com)
approved these changes 2020-08-25 16:40:11 +05:00
vsafonkin
(Migrated from github.com)
approved these changes 2020-08-25 16:40:35 +05:00
AlenaSviridenko
(Migrated from github.com)
approved these changes 2020-08-25 17:56:25 +05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In scope of this PR we've moved node-versions CI from AzureDevOps to GitHub Actions
Details:
The main goal of these changes is to switch the repository to use the system account to publish Node.js releases and create PRs with updating the
versions-manifest.jsonfile. For this purpose we useGITHUB_TOKENwhich is automatically generated by GitHub. Example of PR created using a system account: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 the
workflow_dispatchevent.GitHub Actions CI approach:
We've configured two workflows:
build-node-packages.yml- to build, test and publish Node.js packagescreate-pr.yml- to create PRs with updating theversions-manifest.jsonfileAll workflows are configured using the
workflow_dispatchevent and can be started manually, for example:We did not move
get-node-versionspipeline, it is still on the AzureDevOps