You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are currently “Main” and “Remote” tabs, which teach the basics of Git, which is already very good.
Would it be better if we could add another tab called "Case" that can visualize best practices and classic project cases?
The following are the contents of practical cases:
Best Practices for Git Branching
There are already very mature solutions for best management practices in Git. I hope to use a visual interface and typical project best practices for Git management, so that beginners can quickly improve their ability to manage Git branches.
Best practices for resolving Git conflicts
This is a very high-frequency issue in work and a must-have for many beginners.
For example, I started working from point B, but the collaborator changed point B or even point A, resulting in a conflict of content. I hope to understand the problem through a visual interface and assist me in resolving conflicts step by step.
I think your front-end framework supports this type of interaction capability, right? Let's see if your project plan has taken it into consideration. Hope to be adopted, thank you.
The text was updated successfully, but these errors were encountered:
There are currently “Main” and “Remote” tabs, which teach the basics of Git, which is already very good.
Would it be better if we could add another tab called "Case" that can visualize best practices and classic project cases?
The following are the contents of practical cases:
Best Practices for Git Branching
There are already very mature solutions for best management practices in Git. I hope to use a visual interface and typical project best practices for Git management, so that beginners can quickly improve their ability to manage Git branches.
Best practices for resolving Git conflicts
This is a very high-frequency issue in work and a must-have for many beginners.
For example, I started working from point B, but the collaborator changed point B or even point A, resulting in a conflict of content. I hope to understand the problem through a visual interface and assist me in resolving conflicts step by step.
I think your front-end framework supports this type of interaction capability, right? Let's see if your project plan has taken it into consideration. Hope to be adopted, thank you.
The text was updated successfully, but these errors were encountered: