Merge pull request #5329 from rubberduck-vba/next

v2.5.0

.github/ISSUE_TEMPLATE/bug_report.md

@@ -6,6 +6,7 @@ labels: bug
 assignees: ''
 
 ---
+
 **Rubberduck version information**
 The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:
 

.github/ISSUE_TEMPLATE/feature-request--inspection-.md

@@ -0,0 +1,47 @@
+---
+name: Feature request (inspection)
+about: Suggest something Rubberduck could find in user code and warn about
+title: ''
+labels: enhancement, feature-inspections, up-for-grabs
+assignees: ''
+
+---
+
+**What**
+Describe what the new inspection should find in the user's VBA code; identify the type of inspection: is it about code quality (e.g. potential bugs), is it more of a language opportunity (e.g. obsolete statements), a performance opportunity (e.g. iterating an array with a `For Each` loop), or a Rubberduck opportunity (e.g. something Rubberduck can do or help with, but needs the user code to be modified a bit).
+
+**Why**
+Describe the rationale behind this inspection - *why* finding what we're looking for in the user's code is noteworthy: justify the inspection.
+
+**Example**
+This code should trigger the inspection:
+
+```vb
+Public Sub DoSomething()
+    '...
+End Sub
+```
+
+---
+
+**QuickFixes**
+Should Rubberduck offer one or more quickfix(es) for this inspection? Describe them here (note: all inspections allow for `IgnoreOnceQuickFix`, unless explicitly specified):
+
+1. **QuickFix Name**
+
+    Example code, after quickfix is applied:
+
+    ```vb
+    Public Sub DoSomething()
+        '...
+    End Sub
+    ```
+
+---
+
+**Resources**
+Each inspection needs a number of resource strings - please provide a suggestion here:
+
+ - **InspectionNames**: the name of the inspection, as it appears in the inspection settings.
+ - **InspectionInfo**: the detailed rationale for the inspection, as it appears in the inspection results toolwindow's bottom panel.
+ - **InspectionResults**: the resource string for an inspection result; if the string needs placeholders, identify what goes in for them (e.g. `Variable {0} is not used`, {0}:the name of the variable).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for a new feature other than a new code inspection
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Justification**
+A clear and concise description of the problem that justifies the introduction of this feature.
+
+**Description**
+A clear and concise description of what you want to happen.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/support.md

@@ -0,0 +1,10 @@
+---
+name: Support
+about: Lost? Not sure how to use a feature? We can help!
+title: ''
+labels: support
+assignees: ''
+
+---
+
+Ask us anything! Describe what you're trying to do, include screenshots, relevant code - anything that helps us help you.

.github/ISSUE_TEMPLATE/thanks-.md

@@ -0,0 +1,12 @@
+---
+name: Thanks!
+about: Thank the devs
+title: ''
+labels: thanks
+assignees: ''
+
+---
+
+Our use of GitHub "issues" includes meta-discussions, feature ideas, bugs of course, ...it's also perfectly fine to make one just to drop a "thanks!" to the team, too! Got a story to tell? We want to hear it!
+
+Thank *you* for your support! Rubberduck exists *because* it's free, open-source software. [Here are the real heroes](https://github.com/rubberduck-vba/Rubberduck/stargazers), join them!

.gitignore

@@ -184,5 +184,9 @@ CodeGraphData/
 /Rubberduck.Deployment/Rubberduck.API.idl
 /Rubberduck.Deployment/Rubberduck.idl
 
+# Generated Artifacts
+Rubberduck.CodeAnalysis.xml
+
 #Gradle 
 /.gradle/
+/Rubberduck.CodeAnalysis/Rubberduck.CodeAnalysis.xml

README.md

@@ -59,6 +59,6 @@ along with this program.  If not, see http://www.gnu.org/licenses/.
 
 [![JetBrains ReSharper logo](https://cloud.githubusercontent.com/assets/5751684/20271309/616bb740-aa58-11e6-91c9-65287b740985.png)](https://www.jetbrains.com/resharper/)
 
-Since the project's early days, JetBrains' Open-Source team has been supporting Rubberduck - and we deeply thank them for that. ReSharper has been not only a tool we couldn't do without; it's been an inspiration, the ultimate level of polished perfection to strive for in our own IDE add-in project. So just like you're missing out if you write VBA and you're not using Rubberduck, you're missing out if you write C# and aren't using ReSharper.
+Since the project's early days, JetBrains' Open-Source team has been supporting Rubberduck with free OSS licenses for all core contributors - and we deeply thank them for that. ReSharper has been not only a tool we couldn't do without; it's been an inspiration, the ultimate level of polished perfection to strive for in our own IDE add-in project. So just like you're missing out if you write VBA and you're not using Rubberduck, you're missing out if you write C# and aren't using ReSharper.
 
 <sub>Note: Rubberduck is not a JetBrains product. JetBrains does not contribute and is not affiliated to the Rubberduck project in any way.</sub>