Skip to content

Conversation

@swastikyadav-7
Copy link

@swastikyadav-7 swastikyadav-7 commented Jul 19, 2025

This PR adds a GitHub Actions workflow to welcome users when they open their first issue or pull request. It improves community experience for first-time contributors.
Fixes #100

Summary by CodeRabbit

  • Chores
    • Introduced an automated workflow to welcome new contributors when they open issues or pull requests.

@coderabbitai
Copy link

coderabbitai bot commented Jul 19, 2025

"""

Walkthrough

A new GitHub Actions workflow named "Welcome New Contributors" has been added. This workflow automatically posts a welcome message when a user opens their first issue or pull request, using the actions/first-interaction@v1 action. It is configured to run on Ubuntu and uses the repository's GitHub token.

Changes

File(s) Change Summary
.github/workflows/first-interaction.yml Added workflow to greet users on their first issue or pull request

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant Workflow
    participant FirstInteractionAction

    User->>GitHub: Open Issue or Pull Request
    GitHub->>Workflow: Trigger "Welcome New Contributors"
    Workflow->>FirstInteractionAction: Run action with GitHub token
    FirstInteractionAction->>GitHub: Post welcome message to Issue/PR
Loading

Poem

🐇
A new friend hops into our code,
With a greeting, our bot bestowed.
Issues or PRs, the welcome is clear,
“Thanks for joining us—so glad you’re here!”
Now every new face gets a cheer,
Making our garden bright and sincere.
🌱
"""


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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
.github/workflows/first-interaction.yml (2)

18-19: Remove trailing whitespace to satisfy linters

YAMLlint is already flagging these lines. Strip the spaces at EOL to keep the workflow lint-clean.

-            👋 Hello and welcome! Thank you for opening your first issue.··
+            👋 Hello and welcome! Thank you for opening your first issue.-            🎉 Thanks for your first pull request!··
+            🎉 Thanks for your first pull request!

Also applies to: 22-22


3-7: Consider welcoming users on reopened PRs / issues as well

Edge-case: a contributor might close and later reopen their first PR/issue, receiving no greeting because the event type is limited to opened.
If desirable, broaden the trigger:

on:
  issues:
    types: [opened, reopened]
  pull_request:
    types: [opened, reopened]
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2f1c133 and fd81182.

📒 Files selected for processing (1)
  • .github/workflows/first-interaction.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/first-interaction.yml

[error] 18-18: trailing spaces

(trailing-spaces)


[error] 22-22: trailing spaces

(trailing-spaces)

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/first-interaction.yml (2)

17-17: Pin the action to a commit SHA for supply-chain safety

Relying on a mutable tag (@v1) means the referenced code can change without notice. Pinning to the action’s commit SHA guards against malicious or breaking upstream changes.

-        uses: actions/first-interaction@v1
+        # Pinned for security – update periodically
+        uses: actions/first-interaction@9e0bbf9a5fdb2b4e2a94b4d7a5da9c927c4e8e34

20-26: Trim trailing whitespace to pass YAML-lint

yamllint flags trailing spaces on lines 21 & 25.

-            👋 Hello and welcome! Thank you for opening your first issue.··
+            👋 Hello and welcome! Thank you for opening your first issue.
@@
-            🎉 Thanks for your first pull request!··
+            🎉 Thanks for your first pull request!
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fd81182 and 5215409.

📒 Files selected for processing (1)
  • .github/workflows/first-interaction.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/first-interaction.yml

[error] 21-21: trailing spaces

(trailing-spaces)


[error] 25-25: trailing spaces

(trailing-spaces)

🔇 Additional comments (1)
.github/workflows/first-interaction.yml (1)

11-13: 👍 Permissions block added correctly

The explicit permissions block solves the write-scope problem highlighted in the previous review and should let the workflow post comments successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: Greet New Contributors Workflow

1 participant