chore: add pr-comments workflow with default messages

[MantisClone]

Description

This Pull Request adds the pr-comments.yml workflow which posts customizable comments on Pull Requests submitted by external contributors (those outside the RequestNetwork organization).

The workflow leaves comments in these situations:

• On a contributor's first Pull Request to your repository
• When a Pull Request is marked as ready for review
• When a Pull Request is merged

Details

It uses the GH_PAT_AUTO_COMMENTS organization secret which is a Personal Access Token provided by @MantisClone (me). Thus, the comments look like they're being posted by me.

Default messages

First PR Comment:

'Hello @{{username}}, thank you for submitting your first pull request to the {{repository}} repository. We value your contribution and encourage you to review our contribution guidelines to ensure your submission meets our standards. Please note that every merged PR is automatically enrolled in our Best PR Initiative, offering a chance to win $500 each quarter. Our team is available via GitHub Discussions or Discord if you have any questions. Welcome aboard!'

Ready for Review Comment:

'Thank you for your submission! As you prepare for the review process, please ensure that your PR title, description, and any linked issues fully comply with our contribution guidelines. A clear explanation of your changes and their context will help expedite the review process. Every merged PR is automatically entered into our Best PR Initiative, offering a chance to win $500 every quarter. We appreciate your attention to detail and look forward to reviewing your contribution!'

Merged Comment:

'Congratulations, your pull request has been merged! Thank you for your valuable contribution to Request Network. As a reminder, every merged PR is automatically entered into our Best PR Initiative, offering a quarterly prize of $500. Your work significantly supports our project''s growth, and we encourage you to continue engaging with our community. Additionally, if you want to build or add crypto payments and invoicing features, explore how our API can reduce deployment time from months to hours while offering advanced features. Book a call with our expert to learn more and fast-track your development.'

Test

This test pull request created by an external user shows 3 messages being sent at the appropriate times.

Context

Towards:

• Deploy the "Best PR" Initiative auto-comments#14

Considerations

• Why not use an off-the-shelf action from the Github Actions Marketplace?
  • None of them offered the organization filter. (Considered: welcome-new-users, first-interaction, auto-comments)
• The pr-comments.yml workflow is installed using the @main tag so this repo will pull the latest default messages from the auto-comments repo as soon as they're merged to the main branch.

Reference

• Implementation Repo: https://github.com/RequestNetwork/auto-comments
• Integration Test Repo: https://github.com/RequestNetwork/auto-comments-test

Summary by CodeRabbit

• Chores
  • Enhanced build automation by refining resource management and streamlining environment settings for improved performance.
• New Features
  • Introduced an automated process for pull request feedback, supporting more efficient code reviews and team collaboration.

[coderabbitai]

Walkthrough

The changes update configurations for GitHub Actions workflows and environment settings. In the build workflow, a timeout and container configuration have been removed, a command for unlimited core dumps has been deleted, and the Node.js memory allocation has been increased by updating the NODE_OPTIONS variable. A new workflow, pr-comments.yml, has been added to trigger automated comments on pull request events using an external auto-comments workflow. The nixpacks.toml file has also been updated to adjust the NODE_OPTIONS formatting and remove additional environment variables.

Changes

File(s)	Change Summary
.github/workflows/build.yml	Removed the timeout-minutes setting and container configuration; deleted the ulimit -S -c unlimited command; updated NODE_OPTIONS from --max_old_space_size=7680 to --max-old-space-size=15360; removed NEXT_TELEMETRY_DISABLED and NPM_CONFIG_PRODUCTION.
.github/workflows/pr-comments.yml	Added a new workflow triggered on pull request events (opened, ready for review, closed) that runs a job using an external auto-comments workflow with the secret GH_PAT_AUTO_COMMENTS.
nixpacks.toml	Updated NODE_OPTIONS formatting from --max_old_space_size=2048 to --max-old-space-size=2048; removed NPM_CONFIG_PRODUCTION and NEXT_TELEMETRY_DISABLED variable declarations.

Sequence Diagram(s)

sequenceDiagram
    participant PR as Pull Request Event
    participant GH as GitHub Actions
    participant AC as Auto-Comments Workflow
    PR->>GH: PR Opened / Ready for Review / Closed
    GH->>AC: Trigger pr-comments job using external workflow
    AC-->>GH: Execute auto-comments

Loading

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a56b793 and 21f0024.

📒 Files selected for processing (3)

• .github/workflows/build.yml (1 hunks)
• .github/workflows/pr-comments.yml (1 hunks)
• nixpacks.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

🔇 Additional comments (5)

.github/workflows/pr-comments.yml (3)

1-2: Workflow Declaration is Clear and Concise
The workflow’s name ("PR Comments") clearly indicates its purpose. The file structure is simple and adheres to GitHub Actions syntax.

---

3-6: Trigger Events and Conditions Verification
The workflow is set to trigger on pull_request_target for events opened, ready_for_review, and closed. Since the PR objective mentions posting a comment when a pull request is merged, please verify that triggering on "closed" only posts the merge comment (and not for every closed/abandoned PR). This logic might be handled in the referenced reusable workflow, but it’s worth a double-check.

---

7-15: Proper Usage of Reusable Workflow and Secure Secrets
The job correctly utilizes the external workflow from RequestNetwork/auto-comments, passes the organization name as a parameter, and securely provides the GH_PAT_AUTO_COMMENTS token via secrets. This approach leverages code reuse and maintains security best practices.

nixpacks.toml (1)

21-23: NODE_OPTIONS Formatting Update is Correct
The change from --max_old_space_size=2048 to --max-old-space-size=2048 at line 23 improves consistency with conventional Node.js flag naming. Ensure that the reduced memory allocation (2048 MB) in this configuration is intentional and appropriate for the runtime environment defined by nixpacks.

.github/workflows/build.yml (1)

42-48: Updated Memory Allocation Settings with Clear Documentation
The Build job now sets the NODE_OPTIONS to "--max-old-space-size=15360" with explanatory comments detailing the memory allocation rationale. This update appears well considered. Please confirm that the higher memory allocation for the build process compared to the nixpacks.toml setting (15360 MB vs. 2048 MB) is intentional and aligns with your resource management strategy.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.