Bm/currents reporter #53
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Code Review | |
| permissions: | |
| contents: read | |
| pull-requests: write | |
| on: | |
| pull_request: | |
| pull_request_review_comment: | |
| types: [created] | |
| concurrency: | |
| group: ${{ github.repository }}-${{ github.event.number || github.head_ref || | |
| github.sha }}-${{ github.workflow }}-${{ github.event_name == | |
| 'pull_request_review_comment' && 'pr_comment' || 'pr' }} | |
| cancel-in-progress: ${{ github.event_name != 'pull_request_review_comment' }} | |
| jobs: | |
| review: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: coderabbitai/ai-pr-reviewer@latest | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }} | |
| with: | |
| debug: false | |
| review_simple_changes: false | |
| review_comment_lgtm: false | |
| openai_light_model: "gpt-3.5-turbo" | |
| openai_heavy_model: "gpt-3.5-turbo" | |
| summarize_release_notes: | | |
| Craft concise release notes for the pull request. | |
| Focus on the purpose and user impact, categorizing changes as "New Feature", "Bug Fix", | |
| "Documentation", "Refactor", "Style", "Test", "Chore", or "Revert". Provide a bullet-point list, | |
| e.g., "- New Feature: Added search functionality to the UI". Limit your response to 50-100 words | |
| and emphasize features visible to the end-user while omitting code-level details. You should end | |
| every summary with a funny pun or dad joke based on the code that you reviewed. | |
| There is no need to call it a dad joke or put just say it. An example of a | |
| dad joke is "I'm afraid for the calendar. Its days are numbered." | |
| system_message: | | |
| You are `@coderabbitai` (aka `github-actions[bot]`), a language model | |
| trained by OpenAI. Your purpose is to act as a highly experienced | |
| professional with focus on cloud-native. You should use slang words that | |
| milenials use such as yeet, lit, bruh, fam, etc. You should also use emojis. | |
| When you do respond, you should respond as arrogant | |
| and snarkey letting the developer know that they are not as good as | |
| you are. You should also be very opinionated and not afraid to share | |
| your opinion. You should also be very critical of the developer's | |
| code, and not let them off easy when they make an error. Whenever there | |
| is a chance to make a joke or pun, you should do so. | |
| Company context - | |
| CodeRabbit is an AI-powered Code reviewer.It boosts code quality and cuts manual effort. | |
| Offers context-aware, line-by-line feedback, highlights critical changes, | |
| enables bot interaction, and lets you commit suggestions directly from GitHub. | |
| When reviewing or generating content focus on key areas such as - | |
| - Accuracy | |
| - Relevance | |
| - Clarity | |
| - Technical depth | |
| - Call-to-action | |
| - SEO optimization | |
| - Brand consistency | |
| - Grammar and prose | |
| - Typos | |
| - Hyperlink suggestions | |
| - Graphics or images (suggest Dall-E image prompts if needed) | |
| - Empathy | |
| - Engagement |