Add a pre-check if a user can help with a PR

[IT-VBFK]

Inspired from the issue templates of NUKE

Main reason for this change is: If one can help with a PR he should have the possibility of "first blood" on his issue.

IMPORTANT

• If the PR touches the public API, the changes have been approved in a separate issue with the "api-approved" label.
• The code complies with the Coding Guidelines for C#.
• The changes are covered by unit tests which follow the Arrange-Act-Assert syntax and the naming conventions such as is used in these tests.
• If the PR adds a feature or fixes a bug, please update the release notes with a functional description that explains what the change means to consumers of this library, which are published on the website.
• If the PR changes the public API the changes needs to be included by running AcceptApiChanges.ps1 or AcceptApiChanges.sh.
• If the PR affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
  • Please also run ./build.sh --target spellcheck or .\build.ps1 --target spellcheck before pushing and check the good outcome

[coveralls]

Pull Request Test Coverage Report for Build 5903647369

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.234%

---

Totals
Change from base Build 5894820601:	0.0%
Covered Lines:	12937
Relevant Lines:	13180

---

💛 - Coveralls

[github-actions]

Qodana for .NET

13 new problems were found

Inspection name	Severity	Problems
Redundant type declaration body	🔶 Warning	2
Use preferred body style (convert into property, indexer, or event with preferred body style)	◽️ Notice	11

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[dennisdoomen]

I don't quite get what you're trying to accomplish with this...🙃

[IT-VBFK]

Ok
Another try: The goal is, that you can see on open issues if the issue author can help with a PR.
If so, you could probably assign the issue to the author. If not, the issue is "open" for everyone.

Do you understand my point? 😆

[dennisdoomen]

If so, you could probably assign the issue to the author. If not, the issue is "open" for everyone.

Ah, that's awesome.

[dennisdoomen]

Maybe we should instead ask whether they are willing to provide a PR a POC to help demonstrate the suggestion. Because an API suggestion first needs to get approved before we want anybody to work on a real implementation.

[IT-VBFK]

Should this PoC also be a PR or should they link a separate repo?

[dennisdoomen]

I guess it can be either.