What was the problem/requirement? (What/Why)

Currently we have workflows with the same functional code replicated across 14+ repositories. When making a change to a repository we have to replicate the change this many times.

What was the solution? (How)

To lower the maintenance cost of workflow changes we are using reuable workflows. This allows us to store the functional code in a single location and then have each repository reference the reusable workflows

Example:

name: "Release: Publish"
run-name: "Release: ${{ github.event.head_commit.message }}"

on:
  push:
    branches:
      - mainline
    paths:
      - CHANGELOG.md

concurrency:
  group: release

jobs:
  Publish:
    name: Publish Release
    uses: aws-deadline/.github/reusable_publish.yml@mainline
    secrets: inherit

Also added a default PR template and CODEOWNERS

What is the impact of this change?

We can now work with workflows from a single location most of the time to make changes.

How was this change tested?

Tested in a developer account. Continued testing to will be done after merge.

Was this change documented?

No

Is this a breaking change?

No

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.