new: Add standard issue templates, contributing guidelines, and release drafter (#225)

This change adds the standard templates for issues, pull requests, and
contributing guidelines. Additionally, this pull request adds a release
drafter workflow.

Author: lgarber-akamai

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,37 @@
+name: Bug Report
+description: File a bug report
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: input
+    id: package-version
+    attributes:
+      label: Package
+      description: What version of the linode_api4 package are you using?
+      placeholder: 5.3.0
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What should have happened?
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: List any custom configurations and the steps to reproduce this error
+
+  - type: textarea
+    id: error
+    attributes:
+      label: Error Output
+      description: If you received an error output that is too long, use Gists

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,12 @@
+name: Enhancement
+description: Request a feature
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What would you like this feature to do in detail?
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/help.yml

@@ -0,0 +1,12 @@
+name: Help
+description: You're pretty sure it's not a bug but you can't figure out why it's not working
+title: "[Help]: "
+labels: ["help wanted"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What are you attempting to do, what error messages are you getting?
+    validations:
+      required: true

.github/pull_request_template.md

@@ -0,0 +1,13 @@
+## 📝 Description
+
+**What does this PR do and why is this change necessary?**
+
+## ✔️ How to Test
+
+**What are the steps to reproduce the issue or verify the changes?**
+
+**How do I run the relevant unit/integration tests?**
+
+## 📷 Preview
+
+**If applicable, include a screenshot or code snippet of this change. Otherwise, please remove this section.**

.github/release-drafter.yml

@@ -0,0 +1,21 @@
+name-template: 'v$NEXT_PATCH_VERSION'
+tag-template: 'v$NEXT_PATCH_VERSION'
+categories:
+  - title: '🚀 Added'
+    label: 'added-feature'
+  - title: '🧰 Changed'
+    label: 'changed'
+  - title: "⚠️ Deprecated"
+    label: "deprecated"
+  - title: "⚠️ Removed"
+    label: "removed"
+  - title: '🐛 Bug Fixes'
+    label: 'bugfix'
+  - title: "⚠️ Security"
+    label: "security"
+change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+no-changes-template: "- No changes"
+template: |
+  ## Changes
+
+  $CHANGES

.github/workflows/release-drafter.yml

@@ -0,0 +1,16 @@
+name: Release Drafter
+
+on:
+  push:
+    branches:
+      - main # Preemptive for branch change
+
+jobs:
+  update_release_draft:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: release-drafter/release-drafter@569eb7ee3a85817ab916c8f8ff03a5bd96c9c83e # pin@v5
+        with:
+          config-name: release-drafter.yml
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing Guidelines
+
+:+1::tada: First off, we appreciate you taking the time to contribute! THANK YOU! :tada::+1:
+
+We put together the handy guide below to help you get support for your work. Read on!
+
+## I Just Want to Ask the Maintainers a Question
+
+The [Linode Community](https://www.linode.com/community/questions/) is a great place to get additional support.
+
+## How Do I Submit A (Good) Bug Report or Feature Request
+
+Please open a [GitHub issue](../../issues/new/choose) to report bugs or suggest features.
+
+Please accurately fill out the appropriate GitHub issue form.
+
+When filing an issue or feature request, help us avoid duplication and redundant effort -- check existing open or recently closed issues first.
+
+Detailed bug reports and requests are easier for us to work with. Please include the following in your issue:
+
+* A reproducible test case or series of steps
+* The version of our code being used
+* Any modifications you've made, relevant to the bug
+* Anything unusual about your environment or deployment
+* Screenshots and code samples where illustrative and helpful
+
+## How to Open a Pull Request
+
+We follow the [fork and pull model](https://opensource.guide/how-to-contribute/#opening-a-pull-request) for open source contributions.
+
+Tips for a faster merge:
+* address one feature or bug per pull request.
+* large formatting changes make it hard for us to focus on your work.
+* follow language coding conventions.
+* make sure that tests pass.
+* make sure your commits are atomic, [addressing one change per commit](https://chris.beams.io/posts/git-commit/).
+* add tests!
+
+## Code of Conduct
+
+This project follows the [Linode Community Code of Conduct](https://www.linode.com/community/questions/conduct).
+
+## Vulnerability Reporting
+
+If you discover a potential security issue in this project we ask that you notify Linode Security via our [vulnerability reporting process](https://hackerone.com/linode). Please do **not** create a public github issue.
+
+## Licensing
+
+See the [LICENSE file](/LICENSE) for our project's licensing.

README.rst

@@ -103,3 +103,10 @@ documentation for this library is out of date or unclear, please
 
 .. _Sphinx: http://www.sphinx-doc.org/en/master/index.html
 .. _open an issue: https://github.com/linode/linode_api4-python/issues/new
+
+Contributing
+------------
+
+Please follow the `Contributing Guidelines`_ when making a contribution.
+
+.. _Contributing Guidelines: https://github.com/linode/linode_api4-python/blob/master/CONTRIBUTING.md