Pros of TeamCity

• Runs tests automatically
• Can run deployments
• Receive feedback
• Have multiple ways to run a build (automated vs manual)

Day One experience

• Did not have permissions
• Got permissions to view
• Could not set up project

Writing a manifest

• YML based
• Goes in .github/actions/FILENAME.yml

First part

Writing the name of the action + when its triggered

name: "Name of action when displayed in UI"
# Below is when action is triggered
on:
  push:
    branches:
      - master
    tags:
      - v[0-9]+.[0-9]+.[0-9]+
  pull_request: {}
  schedule:
      - cron: "0 * * * *"

Writing the job(s)

A job consists of one or more steps

jobs:
  build:
    runs-on: ubuntu-18.04
    steps:
      - uses: actions/checkout@v1
      - uses: actions/setup-python@v1

  with:
    python-version: '3.6'
    architecture: 'x64'
  - name: Set up flask environment variables
    run: |
      echo "FLASK_ENV=development" > .env
  - name: Install dependencies
    run: |
      pip install pipenv
      pipenv sync --dev --bare
  - name: Run unit tests via coverage
    run: |
      find tests -name "*.py" | xargs pipenv run coverage run -m pytest
...