ci: improve PR workflows with contributor greeting and title linter fix

[yorukot]

improve PR workflows with contributor greeting and title linter fix

Summary by CodeRabbit

• New Features
  • Introduced automated welcome messages for first-time contributors who open issues or pull requests, providing helpful links and guidance.
• Chores
  • Updated workflow configuration for PR title linting by simplifying permission settings.

[coderabbitai]

Warning

Rate limit exceeded

@yorukot has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 0 minutes and 49 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 8afdb74 and ce46351.

📒 Files selected for processing (3)

• .github/workflows/first-interaction.yml (1 hunks)
• .github/workflows/superfile-build-test.yml (1 hunks)
• .github/workflows/testsuite-run.yml (1 hunks)

Walkthrough

A new GitHub Actions workflow was added to greet first-time contributors with tailored messages for issues and pull requests. Additionally, the linting workflow for PR titles was updated by removing a redundant job-level permissions block, relying on the existing workflow-level permissions instead.

Changes

File(s)	Change Summary
.github/workflows/first-interaction.yml	Added workflow to greet first-time contributors to issues and pull requests with custom messages.
.github/workflows/lint-pr-title.yml	Removed explicit job-level permissions for pull-requests; relies on workflow-level permissions setting.

Suggested reviewers

• lazysegtree

Poem

A hop and a skip, a workflow anew,
Welcoming friends as all bunnies do!
Linting gets lighter, permissions in tow,
The garden grows tidy, with greetings that flow.
🐇✨

— A rabbit who loves a well-kept burrow

---

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.
  • 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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

.github/workflows/first-interaction.yml (2)

21-21: Remove trailing whitespace.

YAML lint flags trailing spaces at the end of this line. Please trim them:

-            That’s totally normal and helps us solve the problem more effectively.  
+            That’s totally normal and helps us solve the problem more effectively.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 21-21: trailing spaces

(trailing-spaces)

---

31-31: Remove trailing whitespace.

YAML lint flags trailing spaces at the end of this line. Please trim them:

-            A maintainer might ask you to make a few changes before we can merge this PR.  
+            A maintainer might ask you to make a few changes before we can merge this PR.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 31-31: trailing spaces

(trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a9f4d96 and 8afdb74.

📒 Files selected for processing (2)

• .github/workflows/first-interaction.yml (1 hunks)
• .github/workflows/lint-pr-title.yml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/lint-pr-title.yml

🧰 Additional context used

🪛 GitHub Check: CodeQL

.github/workflows/first-interaction.yml

[warning] 11-36: Workflow does not contain permissions
Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {{}}

🪛 YAMLlint (1.37.1)

.github/workflows/first-interaction.yml

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

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

• GitHub Check: Analyze (go)

🔇 Additional comments (2)

.github/workflows/first-interaction.yml (2)

1-8: Approve: Contributor greeting workflow metadata.

The workflow name and triggers for first-time issues/PRs correctly implement the contributor greeting feature as intended.

---

13-17: Approve: Using first-interaction action.

The actions/first-interaction@v1 step is correctly configured with repo-token and custom messages for issues and PRs.