Add assign-me-action

.github/workflows/assign-issue.yml

@@ -0,0 +1,34 @@
+name: Assign Issue
+
+on:
+  schedule:
+    - cron: 0 0 * * *
+  issue_comment:
+    types: [created]
+  workflow_dispatch:
+
+jobs:
+  assign:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Assign the user or unassign stale assignments
+        uses: takanome-dev/[email protected]
+        with:
+          github_token: '${{ secrets.GITHUB_TOKEN }}'
+          days_until_unassign: 30
+          assigned_comment: |
+            👋 Hey @{{ comment.user.login }},
+
+            Thanks for your interest in this issue! 🎉
+
+            Newcomers, we're excited to have you on board. Start by exploring our [Contributing](https://github.com/JabRef/jabref/blob/main/CONTRIBUTING.md) guidelines, and don't forget to check out our [workspace setup guidelines](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace) to get started smoothly.
+
+            In case you encounter failing tests during development, please check our [developer FAQs](https://devdocs.jabref.org/code-howtos/faq.html)!
+
+            Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on [JabRef's Gitter chat](https://gitter.im/JabRef/jabref). And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.
+
+            ⚠ Note that this issue will become unassigned if it isn't closed within **{{ totalDays }} days**.
+
+            🔧 A maintainer can also add the **{{ inputs.pin_label }}** label to prevent it from being unassigned automatically.
+
+            Happy coding! 🚀

CONTRIBUTING.md

@@ -8,6 +8,14 @@ If you are not familiar with this type of workflow, take a look at GitHub's exce
 Before you start, get the JabRef code on your local machine.
 Detailed instructions about this step can be found in our [guidelines for setting up a local workspace](getting-into-the-code/guidelines-for-setting-up-a-local-workspace/).
 
+## Table of Contents
+
+- [Choosing a task](#choosing-a-task-join-the-chat-at-httpsgitterimjabrefjabref)
+- [Getting a task assigned](#getting-a-task-assigned)
+- [Pull Request Process](#pull-request-process)
+  - [Requirements on the pull request and code](#requirements-on-the-pull-request-and-code)
+  - [Development hints](#development-hints)
+
 ## Choosing a task [![Join the chat at https://gitter.im/JabRef/jabref](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/JabRef/jabref)
 
 In general, we offer small issues perfect for aspiring developers.
@@ -48,6 +56,11 @@ GitHub offers a good guide at [Editing files in another user's repository](https
 
 One can also add [callouts](https://just-the-docs.github.io/just-the-docs-tests/components/callouts/).
 
+## Getting a task assigned
+
+Comment on the issue you want to work at with `/assign-me`.
+GitHub will then automatically assign you.
+
 ## Pull Request Process
 
 1. **Create a new branch** (such as `fix-for-issue-121`). Be sure to create a **separate branch** for each improvement you implement.