[CES-51] Azure DevOps pipelines migrated into GitHub Actions #79
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.
List of Changes
The two workflows on Azure DevOps
code-review
deploy-pipelines
have been recreated in the form of GitHub Actions, but
deploy-pipelines
is now divided into two actions one for the web app deploy on azure and one for npm publish sdk.They have been inserted in the
.github/workflows
folder.Added
pre-commit
configuration.Added
infra
folder withidentity
andrepository
infrastructure, and added branch protection onmaster
(already applied).Edited
.gitignore
andCODEOWNER
files.Motivation and Context
Since all the pipelines on Azure DevOps are gradually being decommissioned, it was decided to recreate them on the different repos such as GitHub Actions.
How Has This Been Tested?
Currently they have been tested by inserting
so as to execute them automatically at each test push.
To do the Deploy test for
deploy-pipelines
action i've used this step only to check if all will be called correctly:Screenshots (if appropriate):
Types of changes
Checklist: