Sync Collection with changes to prefect-collection-template (PrefectHQ#72)

* Updating collection with changes to prefect-collection-template

* Fix cruft

* Updating collection with changes to prefect-collection-template

* Updating collection with changes to prefect-collection-template

* Updating collection with changes to prefect-collection-template

* Remove rej

* Updating collection with changes to prefect-collection-template

* Remove rejk

Co-authored-by: ahuang11 <ahuang11@users.noreply.github.com>
Co-authored-by: ahuang11 <andrew.h@prefect.io>

Author: 3 people

.cruft.json

@@ -1,6 +1,6 @@
 {
   "template": "https://github.com/PrefectHQ/prefect-collection-template",
-  "commit": "f1db52cbcc7d45eaf7d1ffa494e5faf2627600a3",
+  "commit": "dabff0c99e3eb545d926ec6026bf8843e84eeb6a",
   "checkout": null,
   "context": {
     "cookiecutter": {

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,32 +1,28 @@
-<!-- 
-Thanks for opening a pull request to prefect-gcp 🎉!
+<!-- Thanks for contributing 🎉! Please ensure the title neatly summarizes the proposed changes. -->
 
-We've got a few requests to help us review contributions:
+<!-- Overview -->
 
-- Make sure that your title neatly summarizes the proposed changes.
-- Provide a short overview of the change and the value it adds.
-- Share an example to help us understand the change in user experience.
-- Run `pre-commit install && pre-commit run --all` for linting.
-
-Happy engineering!
--->
-
-<!-- Include an overview here -->
-
-<!-- Link to issue -->
-Closes #
+Closes
 
 ### Example
-<!-- 
-Share an example of the change in action.
-
-A code blurb is best. Changes to features should include an example that is executable by a new user.
+<!-- A code blurb is best. Changes to features should include an example that is executable by a new user. -->
+
+### Screenshots
+<!--
+Any relevant screenshots
+  - The updated docs page from `mkdocs serve`.
+  - Output from running the example.
+  - Service integration test results.
 -->
 
 ### Checklist
 <!-- These boxes may be checked after opening the pull request. -->
 
-- [ ] This pull request references any related issue by including "Closes #<ISSUE_NUMBER>"
-	- If no issue exists and your change is not a small fix, please [create an issue](https://github.com/PrefectHQ/prefect-gcp/issues/new/choose) first.
-- [ ] This pull request includes tests or only affects documentation.
-- [ ] Summarized PR's changes in [CHANGELOG.md](https://github.com/PrefectHQ/prefect-gcp/blob/main/CHANGELOG.md)
+- [ ] References any related issue by including "Closes #<Issue Number>" or "Closes <Issue URL>".
+  - If no issue exists and your change is not a small fix, please [create an issue](https://github.com/PrefectHQ/prefect-gcp/issues/new/choose) first.
+- [ ] Includes tests or only affects documentation.
+- [ ] Passes `pre-commit` checks.
+  - Run `pre-commit install && pre-commit run --all` locally for formatting and linting.
+- [ ] Includes screenshots of documentation updates.
+  - Run `mkdocs serve` view documentation locally.
+- [ ] Summarizes PR's changes in [CHANGELOG.md](https://github.com/PrefectHQ/prefect-gcp/blob/main/CHANGELOG.md)

MAINTAINERS.md

@@ -2,6 +2,8 @@
 
 ## Getting Started
 
+Now that you've bootstrapped a project, follow the steps below to get started developing your Prefect Collection!
+
 ### Python setup
 
 Requires an installation of Python 3.7+
@@ -10,10 +12,12 @@ We recommend using a Python virtual environment manager such as pipenv, conda or
 
 ### GitHub setup
 
-Generate a Prefect collection project in the terminal:
+Create a Git respoitory for the newly generated collection and create the first commit:
 
 ```bash
-cookiecutter https://github.com/PrefectHQ/prefect-collection-template
+git init
+git add .
+git commit -m "Initial commit: project generated by prefect-collection-template"
 ```
 
 Then, create a new repo following the prompts at: