Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add NGINX bot #1607

Merged
merged 7 commits into from
Feb 22, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions .github/workflows/nginx-bot.yml
Original file line number Diff line number Diff line change
@@ -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
lucacome marked this conversation as resolved.
Show resolved Hide resolved
with:
pr-assignee-from-issue: 583
lucacome marked this conversation as resolved.
Show resolved Hide resolved
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.
5 changes: 3 additions & 2 deletions docs/developer/pull-request.md
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down
Loading