Hi all! I’m Ray, a CS student new to OSS contribution, and super excited to be joining this community. I did have one small question: if I’m working on maintenance changes, such as issue #6408 which requires multi file changes incrementally, should I be making a new PR for every file change I make? all changes between files are unrelated, the issue simply talks about catching errors earlier to prevent deprecation.
Would love to hear about your experiences here and with OSS in general, and any advice you might have for someone trying to contribute more!
Hi Ray, it’s awesome that you’re interested in contributing. A PR should be scoped to a single feature. Commits should be logical groupings. There’s a nice discussion about it here that I like.
Don’t worry about PR spam unless you’re setting an openclaw on loop or something. Then we’ll have to talk.
Hahaha, the openclaw method is certainly something (not a good something). Thanks for the reply - I’ll keep PRs scoped to a single feature. If possible, let me know if this PR follows the standards here, it’s my first one: TEST: Fail on unexpected warnings in test_math.py by sankhyanreyansh · Pull Request #8392 · pymc-devs/pymc · GitHub