Over the course of development, the team always plagued by our source control namely Git. At the early stage of the development, we settled on using GitLab because it provides a big data limit than GitHub as well as a private repo. However, we did'nt reply settled on what interface to use. I personally has tried GitHub Desktop and SourceTree but they are either too simplified or too complicated to use. Therefore, I opt for Ungit.
Ungit is a free, web-based source control interface. It is lightweight and most importantly very visual-friendly, which means the operations are clearly visualised by the "branches" and "nodes".
The visualised operations made the entire process more understandable. However, with a more understandable interface, we still faced quite a number of issues along the way.
Issues like overwriting each other's stuff, causing the "unable to be fast-forward remote branch" error, and worst of all reverting our progress. However, along the way we did learn a lot about source control, although we are still rather inexperience with but we had a glimpse of what it can really offer. I'm hoping to fully learn how Git process should be carried to prevent those disasters from happening during my internship period. At these moment, the team can only work with what we know and what we have.
Kommentare