Skip to content

Contributing workflow on PR size and review process expectation - #113

Open
Jerry-Jinfeng-Guo wants to merge 1 commit into
mainfrom
documentation/contributing-guide-pr-size-and-expectations
Open

Contributing workflow on PR size and review process expectation#113
Jerry-Jinfeng-Guo wants to merge 1 commit into
mainfrom
documentation/contributing-guide-pr-size-and-expectations

Conversation

@Jerry-Jinfeng-Guo

Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: Jerry Jinfeng Guo <jerry.jinfeng.guo@alliander.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the contributor guidance by clarifying expectations around PR size/scope and describing the project’s review criteria and workflow, with emphasis on maintainability and reviewer efficiency.

Changes:

  • Adds a new “Contribution Workflow” section describing PR sizing guidelines and review criteria.
  • Moves PR-size/bulk-change guidance into the AI-assisted contribution quality checklist.
  • Documents how maintainers approach functionality vs. style-only adjustments and how “critical components” changes should be coordinated.
Suppressed comments (2)

CONTRIBUTING.md:272

  • This list item wraps onto a new line, but the continuation line isn’t indented, which breaks Markdown list formatting (it will render as a separate paragraph).
* **Stylistic Adjustments**: If your coding style or standards differ from the rest of the codebase, 
we may merge the core functionality first and initiate follow-up PRs or discussions to handle code formatting.

CONTRIBUTING.md:276

  • This list item wraps onto a new line, but the continuation line isn’t indented, which breaks Markdown list formatting.
* **Maintainer Notification**: For changes to critical features or core components, 
we require a heads-up and prior discussion with the maintainers.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread CONTRIBUTING.md
Comment on lines +259 to +262
* **Prefer Smaller PRs**: We highly appreciate contributions that come in a manageable size.
* **Break Up Large Changes**: If your contribution involves substantial code changes,
please split it into multiple smaller, logical Pull Requests.

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.

2 participants