Release 0.3.0

.cookiecutter.json

@@ -5,7 +5,7 @@
     "project_name": "Pylint Nautobot",
     "project_slug": "pylint-nautobot",
     "project_python_name": "pylint_nautobot",
-    "project_python_base_version": "3.7",
+    "project_python_base_version": "3.8",
     "project_with_config_settings": "yes",
     "generate_docs": "no",
     "version": "0.1.0",

.flake8

@@ -1,8 +1,9 @@
 [flake8]
-# E501: Line length is enforced by Black, so flake8 doesn't need to check it
-# W503: Black disagrees with this rule, as does PEP 8; Black wins
-ignore = E501, W503
-exclude =
+ignore =
+  E501,  # Line length is enforced by Black, so flake8 doesn't need to check it
+  W503   # Black disagrees with this rule, as does PEP 8; Black wins
+exclude = 
   __pycache__,
   .venv,
   tests/inputs
+  var

.github/CODEOWNERS

@@ -1,2 +1,2 @@
 # Default owner(s) of all files in this repository
-* @cmsirbu @Kircheneer @nautobot/maintain-core
+* @cmsirbu @Kircheneer @nautobot/maintain-nautobot-apps

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,7 +4,8 @@ about: Report a reproducible bug in the current release of pylint-nautobot
 ---
 
 ### Environment
-* Python version:  <!-- Example: 3.7.7 -->
+* Python version:  <!-- Example: 3.11.4 -->
+* Nautobot version:  <!-- Example: 2.0.0 -->
 * pylint-nautobot version:  <!-- Example: 1.0.0 -->
 
 <!-- What did you expect to happen? -->
@@ -21,4 +22,4 @@ about: Report a reproducible bug in the current release of pylint-nautobot
 ### Steps to Reproduce
 1.
 2.
-3.
+3.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -5,6 +5,7 @@ about: Propose a new feature or enhancement
 ---
 
 ### Environment
+* Nautobot version:  <!-- Example: 2.0.0 -->
 * pylint-nautobot version:  <!-- Example: 1.0.0 -->
 
 <!--

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -1,10 +1,34 @@
-## New Pull Request
+<!--
+    Thank you for your interest in contributing to pylint-nautobot! Please note
+    that our contribution policy recommends that a feature request or bug
+    report be opened for approval prior to filing a pull request. This
+    helps avoid wasting time and effort on something that we might not
+    be able to accept.
 
-Have you:
-- [ ] Updated the README if necessary?
-- [ ] Updated any configuration settings?
-- [ ] Written a unit test?
+    Please indicate the relevant feature request or bug report below.
+-->
 
-## Change Notes
+# Closes: #<ISSUE NUMBER GOES HERE>
 
-## Justification
+## What's Changed
+
+<!--
+    Please include:
+    - A summary of the proposed changes
+    - A sectioned breakdown for larger features under ## subheadings
+    - Screenshots, example payloads where relevant:
+      - Before/After for bugfixes
+      - Using a new feature
+-->
+
+## To Do
+
+<!--
+    Please feel free to update todos to keep track of your own notes for WIP PRs.
+-->
+- [ ] Explanation of Change(s)
+- [ ] Attached Screenshots, Payload Example
+- [ ] Unit, Integration Tests
+- [ ] Documentation Updates (when adding/changing features)
+- [ ] Example App Updates (when adding/changing features)
+- [ ] Outline Remaining Work, Constraints from Design