.github/ CODEOWNERS and pull_request_template.md copied from Glides

.github/CODEOWNERS

@@ -0,0 +1,10 @@
+# The Glides team is the default owner for the entire codebase.
+*       @mbta/glides-developers
+
+# Dependency manifests & CI tooling does not automatically add reviewers
+mix.exs
+mix.lock
+package.json
+package-lock.json
+.tool-versions
+Dockerfile

.github/pull_request_template.md

@@ -0,0 +1,45 @@
+Asana Task: [Title](link)
+
+<!-- Or consider adding links to:
+* Notion
+* Slack discussions
+* Design files
+-->
+
+Description goes here.
+Include screenshots if relevant.
+
+Checklist
+
+<!-- check one from each section with (x) -->
+
+- Tests:
+  - `( )` Has tests
+  - `( )` Doesn't need tests
+  - `( )` Tests deferred (with justification)
+- Product/Design sign off:
+  - `( )` Okayed the plan for the feature (e.g. the design files, or the Asana task)
+  - `( )` Reviewed the feature as implemented (e.g. on dev-green, or saw screenshots)
+  - `( )` No review needed
+
+<!--
+* Should this PR be deployed to dev-green for review? If so, add the `deploy-to-dev-green` label.
+* Does this review need to be prioritized? If so, add the `important` label.
+-->
+
+<!--
+Followup Tasks:
+(add if needed)
+
+Prompts for followup tasks:
+* Does anyone (stakeholders, other teams) need to be told when this work is complete?
+* Do we need to be careful about how we deploy this, for technical or product reasons?
+* Is there other work that's unblocked by this PR?
+* Are there new followup Asana tasks? Link to them.
+-->
+
+<!--
+Keep Asana up to date.
+* After this PR is open, add a link to it from its Asana task and move the task to "Under Review".
+* After it's merged, mark the Asana task complete.
+-->