Comment on PR just opened

[koppor]

Triggered by #13500

If a contributor "just" submits a PR on fixing an issue, we cannot mark the issue to the contributor. Thus other contributors can assign it to themselves (happened at #13486 (comment)).

To avoid that, we can post a message to the PR at these cases.

This is somehow different to other projects, where a PR can be made without "raising hands". In our context 90% of the contributors come. Therefore, the workflow job will only fail on non good first/second/... issues.

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [/] Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• [/] Tests created for changes (if applicable)
• [/] Manually tested changed features in running JabRef (always required)
• [/] Screenshots added in PR description (if change is visible to the user)
• [/] Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• [/] Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨

[subhramit]

So this basically means - no auto-assignment on direct PRs (corresponding to an issue), trigger message on PR to tell the contributor to assign themselves first

[koppor]

So this basically means - no auto-assignment on direct PRs (corresponding to an issue), trigger message on PR to tell the contributor to assign themselves first

Partially: Auto assignment if contributor commented on issue. If contributor did not comment, tell him to assign himself (in the case of good first issue). Otherwise: Stay silent.