Update copilot instructions for PR checks and CI#552
Conversation
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
…e tests Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- Enhance documentation for null type syntax scenarios with detailed explanations - Add curly braces around nested if statement for better code style - Explain when parameter type inference occurs and why returning true is correct Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com>
- Enhance CallbackSignatureShouldMatchMockedMethodAnalyzer to robustly check ref/out/in modifiers and parameter types. - Update CallbackSignatureShouldMatchMockedMethodFixer to preserve ref/out/in modifiers in code fixes. - Expand RefOutCallbackTests to cover edge cases and verify correct
Added a dedicated section outlining mandatory formatting, build, test, and Codacy analysis checks for all PRs. Clarified evidence requirements and CI enforcement. Linked recent PR and CI job examples for reference.
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughA new section outlining mandatory PR checks and CI requirements was added to the contributor instructions in Changes
Possibly related PRs
Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Copilot instructions to add comprehensive PR checks and CI requirements. The update emphasizes strict validation requirements that must be met before code review.
- Adds detailed PR validation checklist including formatting, build, test, and analysis requirements
- Specifies evidence requirements for PR descriptions with console output or screenshots
- Establishes clear consequences for PRs that fail validation (automatic closure)
| `dotnet test --settings ./build/targets/tests/test.runsettings` | ||
| All tests must pass. PRs with failing tests will be closed. | ||
| - **Codacy Analysis:** | ||
| Run Codacy CLI analysis on all changed files. Fix all reported issues before submitting the PR. |
There was a problem hiding this comment.
The Codacy Analysis section lacks specific instructions on how to run the CLI analysis. Consider adding the exact command or referencing where developers can find the instructions.
| Run Codacy CLI analysis on all changed files. Fix all reported issues before submitting the PR. | |
| Run Codacy CLI analysis on all changed files using the following command: | |
| `codacy-analysis-cli analyze --directory <path-to-changed-files>` | |
| Replace `<path-to-changed-files>` with the directory containing the modified files. | |
| For more details, refer to the [Codacy CLI documentation](https://docs.codacy.com/repositories-configure/codacy-analysis-cli/). | |
| Fix all reported issues before submitting the PR. |
| - **No Received Files:** | ||
| Remove any `*.received.*` files before committing. | ||
| - **Moq Version Awareness:** | ||
| If tests are added/changed, specify which Moq versions are targeted and how test data is grouped. |
There was a problem hiding this comment.
The Moq Version Awareness requirement is vague. It doesn't specify how developers should document version targeting or what constitutes proper test data grouping documentation.
| If tests are added/changed, specify which Moq versions are targeted and how test data is grouped. | |
| If tests are added/changed, document the following in the PR description: | |
| - The specific Moq version(s) targeted by the tests. | |
| - A brief explanation of how test data is grouped, including the rationale for the grouping strategy. | |
| Ensure this information is clear and concise to assist reviewers in understanding the changes. |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
Summary by CodeRabbit