mirror of
https://github.com/getpaseo/paseo.git
synced 2026-07-29 12:01:31 +00:00
33 lines
1.2 KiB
Markdown
33 lines
1.2 KiB
Markdown
# Contributing to Paseo
|
|
|
|
Paseo is an opinionated product maintained by one person.
|
|
|
|
I read every issue and PR myself, and I am selective about what contributions I accept.
|
|
|
|
Good ideas still need to fit the shape of the product: a PR can be technically correct and still not belong in Paseo.
|
|
|
|
Core product, design, architecture, and workflow changes are not accepted.
|
|
|
|
Follow these rules if you want your PR to be merged:
|
|
|
|
- Keep it to one focused change
|
|
- Link to an issue
|
|
- Explain the problem you're solving
|
|
- Include repro steps if it's a bug
|
|
- Include QA/testing evidence
|
|
- UI changes need screenshots or video for every affected platform: iOS, Android, desktop, and web
|
|
- If you only tested one platform, say that clearly
|
|
|
|
Your PR will be closed if you do any of these:
|
|
|
|
- Bundle unrelated changes
|
|
- Fail basic checks like typecheck, formatting or linting
|
|
- Make product, design, or architecture changes without prior discussion
|
|
- Submit no evidence of testing
|
|
- Skip the linked issue
|
|
- Clearly fully AI-generated PR
|
|
|
|
## AI assistance
|
|
|
|
AI in the loop is fine. The bar is whether _you_ tested the change and can explain why it works. A confident wall of AI prose with no evidence of testing is a red flag and will get closed.
|