← 返回首页
Separate quality paragraphs and adjust decline wording · gitpython-developers/GitPython@92ff6df · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted
Cancel Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search
Appearance settings
Resetting focus

Commit 92ff6df

Browse files
EliahKagan
and
claude
committed
Separate quality paragraphs and adjust decline wording
Split the quality-expectations section into two paragraphs (the warning about low-quality contributions being declined was visually merged with the preceding paragraph). Replace "and the pull request closed without warning" with a note that maintainers may not always be able to provide detailed feedback, which conveys the same practical reality. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 4941c31 commit 92ff6df

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

‎CONTRIBUTING.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,10 @@ Contributions must be made with care and meet the quality bar of the surrounding
1515
That means a change should not leave GitPython worse than it was before: it should be
1616
readable, maintainable, tested where practical, documented and consistent with the
1717
existing style and behavior.
18+
1819
A contribution that works only narrowly but lowers the quality of the
19-
codebase may be declined, and the pull request closed without warning.
20+
codebase may be declined. The maintainers may not always be able to provide
21+
detailed feedback.
2022

2123
## AI-assisted contributions
2224

0 commit comments

Comments
 (0)

Footer

© 2026 GitHub, Inc.