Closed https-alok closed 1 week ago
The new GitHub Actions workflow, Testing-Comment-PR
, has been added to automate the process of welcoming new contributors to the repository. This workflow triggers on pull_request_target
events and checks if the contributor is new. If so, it posts a welcome comment on their pull request, fostering a friendly and inclusive community.
File | Change Summary |
---|---|
.github/workflows/first.yml |
Introduced a workflow to comment on PRs from new contributors. |
🐇 In the land of code, a new file appears, To welcome new friends, and calm their fears. With a comment so kind, on their PR it lands, From a friendly bot, with helping hands. 🌟
[!TIP]
New Features and Improvements
## Review Settings Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments. ## AST-based Instructions CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the [documentation](https://docs.coderabbit.ai/guides/review-instructions#ast-based). ## Community-driven AST-based Rules We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the [ast-grep-essentials](https://github.com/coderabbitai/ast-grep-essentials) repository for more information. ## New Static Analysis Tools We are continually expanding our support for static analysis tools. We have added support for `biome`, `hadolint`, and `ast-grep`. Update the settings in your `.coderabbit.yaml` file or head over to the settings page to enable or disable the tools you want to use. ## Tone Settings Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples: - Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!" - Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!" - Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!" ## Revamped Settings Page We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to `.coderabbit.yaml` will be reflected in the settings page, and vice versa. ## Miscellaneous - Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the `enable_free_tier` setting. - Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (`local`) or the organization (`global`) level using the `knowledge_base` setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations. - High-level summary placement: You can now customize the location of the high-level summary in the PR description using the `high_level_summary_placeholder` setting (default `@coderabbitai summary`). - Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the `request_changes_workflow` setting.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@coderabbitai can you send me workflow to send message on first pr merge for the contributor
[!TIP] For best results, initiate chat on the files or code changes.
@https-alok, here's a GitHub Actions workflow that sends a message when a contributor's first PR is merged. This workflow uses the pull_request
event with the type closed
to trigger when a PR is merged. It then uses a job to check if this is the contributor's first merged PR and sends a message if it is.
name: Welcome First-Time Contributors
on:
pull_request:
types: [closed]
jobs:
welcome:
if: github.event.pull_request.merged == true
runs-on: ubuntu-latest
steps:
- name: Check if it's the first PR
id: check_first_pr
uses: actions/github-script@v6
with:
script: |
const { data: prs } = await github.rest.pulls.list({
owner: context.repo.owner,
repo: context.repo.repo,
state: 'closed',
creator: context.actor
});
const firstPr = prs.length === 1;
return firstPr;
- name: Post Welcome Message
if: steps.check_first_pr.outputs.result == 'true'
uses: actions/github-script@v6
with:
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
body: '🎉 Congratulations on your first merged pull request! Welcome to the community!'
});
This workflow checks if the PR is merged and then uses the GitHub API to count the number of closed PRs by the PR creator. If it's their first, it posts a welcome message. Adjust the message as needed to fit your community guidelines or personal preferences.
GitHub Issue: # / NA
Summary:
Do you think resolving this issue might require an Architectural Decision Record (ADR)? (significant or noteworthy)
Yes/No [JUSTIFICATION]
Summary by CodeRabbit