About issues and PRs. #677
Replies: 5 comments 4 replies
-
@birm, Also, I have noticed that you're merging Pull Requests into the I ask because even though |
Beta Was this translation helpful? Give feedback.
-
@birm I was contemplating, as we are directing our commits to the develop branch instead of master, and not synchronizing the master with the PRs, wouldn’t there be potential issues if a PRs were to conflict? |
Beta Was this translation helpful? Give feedback.
-
@brim I’ve also proposed an issue to migrate caMicroscope to a some modern-day frontend framework. If this aligns with your vision, I could adopt this as my GSoC project and commence work on it immediately. Please share your thoughts on this. |
Beta Was this translation helpful? Give feedback.
-
@birm I have a rough proposal for the project title as |
Beta Was this translation helpful? Give feedback.
-
You don't need to make an issue before a PR, but you should make sure that between the PR description and the issue (if you decide to open/reference one) it's clear what the issue/problem is and what the fix is. |
Beta Was this translation helpful? Give feedback.
-
Hey, @birm, I’m planning to make some improvements. Is it necessary to open a corresponding issue for every Pull Request, or can I directly open a PR?
Beta Was this translation helpful? Give feedback.
All reactions