For the book updates and community contributions

Note 
Before you begin, complete the 
Publish the app’s code to GitHub
and 
Disconnect local Git 
deployment
sections of the 
Continuous integration and deployment with Azure DevOps
section to 
publish your code to GitHub. Then proceed to the 
Build
article. 
In the 
Build
article, you’ll create the initial workflow to build and test the .NET app. You’ll:
•
Learn the basic structure of a GitHub Action workflow YAML file. 
•
Use a template to create a basic build workflow that builds a .NET app and executes unit tests. 
•
Publish the compiled app so that it’s r
eady for deployment. 
In the 
Deploy
article, you’ll:
•
Learn about environments in GitHub Actions. 
•
Create two environments and specify environment protection rules. 
•
Create environment secrets for managing environment-specific configuration. 
•
Extend the workflow YAML file to add deployment steps. 
•
Add a manual dispatch trigger. 
Secure code with CodeQL 
In addition to building and deploying code, 
GitHub Advanced Security
 
offers tools for “shifting left” 
with security. That is, integrating security early on in the software delivery lifecycle. 
CodeQL
 is a code 
scanning language that runs queries to find potential vulnerabilities or quality issues in your code. 
CodeQL is run using an Actions workflow. 
In the 
CodeQL
article, you’ll:
•
Create a Code Scanning Action. 
•
Edit the workflow file to include custom scan settings. 
•
See scanning results. 

---

35 
CHAPTER 3 | Continuous integration and deployment with Azure DevOps 
Compare and contrast GitHub Actions and Azure Pipelines 
GitHub Actions and Azure Pipelines have a common lineage and are similar in many respects. 
However, you should understand the differences before selecting a platform for building, testing, and 
deploying apps. In the 
Comparison
article, you’ll deep dive into these platforms and compare and 
contrast them. You’ll also learn how to select the correct platform for your CI/CD needs.
Compare and contrast GitHub Actions and Azure 
Pipelines 
GitHub Actions
 and 
Azure Pipelines
 have a common history. In fact, the Actions agent is a fork of the 
Pipelines agent. There are m
any similarities between GitHub Actions and Azure Pipelines and it’s 
worth comparing and contrasting them.