Basic Node App built with Azure DevOps for showcasing the GitHub Flow.

This repository is set up to illustrate a collaboration flow using GitHub Issues & Project Boards or the integration with ⚡️ Azure Board:

1. Create a new Issue (and link it to the Kanban Board) or Work Item; take note of the ID and export ISSUE_ID="[ISSUE_ID_HERE]"
2. Let's create a new branch locally starting from our demo-init branch which contains some predefined changes:

git checkout -b ado-demo-$ISSUE_ID
git apply demo.patch

3. this creates a new local branch with some pre-modified changes. Commit the changes (using the Fixes #123 syntax if using GitHub Issues or Fixes AB#123 for Azure Boards) and push the new branch
4. Open a Pull Request:

• Codecov should report an increased threshold
• Snyk should fail because of the fixed version
• pjawesome will be assigned as Code Owner for review – you can override this and assign to someone else
• Azure Pipelines will build and automatically deploy to the Staging environment

5. Using suggested changes, fix the package.json version by restoring the ^ sign
6. Approve the PR and wait for the staging environment to be available

If you merge the PR (optional) it is recommended to create a new Pull Request (master is a protected branch) that commits the "revert" of the same demo patch to restore master to the initial state: simply do a git apply -R demo.patch, create a new branch, commit and merge.

Feel free to fork this repo for personal demos. The master branch contains the Azure Pipelines build YAML files (ado-*.yaml) while the release pipeline JSON files are under the /pipelines folder - you can use the Azure Pipelines import function to import and create the 2 pipelines.

Code Coverage on master

Build status for master