-
So I've been working on code and pushing it quite often. I do sometimes break the app when I oversee some bug (like here), should I also be submitting PRs for review? Not really sure what the common practice is on this one, what do you guys think? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 11 replies
-
@ryansurf While that's fine for personal development, it can cause issues for external contributors if a bug occurs in an OSS project...😱 If possible, could you add me as an "external collaborator" (maintainer) for this repository? That way, I can be assigned as a reviewer using GitHub's functionality, and I would be happy to take on the review tasks. |
Beta Was this translation helpful? Give feedback.
-
Rest assured. External collaborators can be given detailed permissions, so there is no problem as long as the minimum necessary permissions are granted to them:) |
Beta Was this translation helpful? Give feedback.
-
@ryansurf |
Beta Was this translation helpful? Give feedback.
@ryansurf
Yes, that's right. Without a review process, there's a risk of missing bugs and breaking the app. Therefore, even if you're the project owner, it's a common practice to submit PRs and merge them into the main branch only after they've been reviewed and approved by a reviewer (maintainer).
While that's fine for personal development, it can cause issues for external contributors if a bug occurs in an OSS project...😱
If possible, could you add me as an "external collaborator" (maintainer) for this repository? That way, I can be assigned as a reviewer using GitHub's functionality, and I would be happy to take on the review tasks.