Add NGINX bot

.github/workflows/nginx-bot.yml

@@ -0,0 +1,35 @@
+name: NGINX Bot
+
+on:
+  issues:
+    types:
+      - opened
+      - reopened
+      - edited
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - edited
+
+concurrency:
+  group: ${{ github.event.issue.number || github.event.pull_request.number }}-bot
+  cancel-in-progress: true
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  comment:
+    name: Run the bot
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Bot Action
+        uses: lucacome/nginx-bot@main
+        with:
+          pr-assignee-from-issue: 583
+          warn-missing-issue: true
+          missing-issue-message: |
+            Please make sure to include the issue number in the PR description to automatically close the issue when the PR is merged.
+            See [Linking a pull request to an issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) and our [Pull Request Guidelines](../docs/developer/pull-request.md) for more information.

docs/developer/pull-request.md

@@ -8,8 +8,9 @@
   in the curated [release notes](../CHANGELOG.md), add a brief note that summarizes the change in the `release-note` block
   in the PR description.
 - Fill in [our pull request template](/.github/PULL_REQUEST_TEMPLATE.md).
-- Make sure to include the issue number in the PR description to automatically close the issue when the PR mergers.
-  See [Closing Issues via Pull Requests](https://github.blog/2013-05-14-closing-issues-via-pull-requests/) for details.
+- Make sure to create an issue and include the issue number in the PR description to automatically close the issue when the PR is merged.
+  See [Linking a pull request to an issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) for details.
+  An issue might not be required for PRs addressing typos, broken links, etc.
 - For significant changes, break your changes into a logical series of smaller commits. By approaching the changes
   incrementally, it becomes easier to comprehend and review the code.
 - Use your best judgement when resolving comments. Simple, unambiguous comments should be resolved by the submitter,