Git Merge

We attend the Git Merge 2018

Article

We extract the trends in Git that stand out this 2018.

Once again the Git Merge 2018 took place. Two days exclusively dedicated to talk about the control tool Git. From technical sessions to workshops, all kind of developers discover new ways to use Git at their work.

For once, the event was held in Barcelona, leading city in digital innovation. Two of our colleagues from ALM team, Adrià Figuera and Guillem Tanyà, attended the event, where they extracted the trends that stand out in Git this 2018.

The influence of communities in Open Source

Do you remember the old game ZZT? Where players were able to build their own game. With this creative parallelism, began the talk that presented the non-profit entity that oversees FLOSS development. Highlighting the relevance of the contributions of the communities and the importance of Open source software.

Simplify Backups with large amount of data.

Not everything was theory. The engineer Carlos Martin, explained a case study of how to structure the backups of repositories in GitHub and the problems that can arise. Initially, they used a Sharding model of data from their own file systems and returned it to Amazon. But there was a big problem, the high volume of data and the slow recovery. So they pass to a model whereby you can do incremental backups of different parts of a git repository (objects, references, etc.) against Amazon S3 and an auxiliary support DB. Thanks to the new model, they can give better support to the thousand daily recoveries.

Git, a tool for designers

Can be useful Git for a designer? Yes it is. The concepts that are being applied in the world of programming, can be applied in a designer work. Which designer has not ever had a component of an interface without updating? Using sketching tools, you can unify efforts through git repositories.

Useful for an entire company

Is possible another way around to the utility of GitLab in a company. The platform is no longer an exclusive tool for developers. The key to all this? The issues. Depart from an issue, any employee contribute to detect a bug or a needed change in the software.

It was also explained how simple and enjoyable Markdown can be used by any profile, whether technological or not. From the commercial to the engineer can edit the web using this tools.

Git driven refactoring

With the focus on the basic principles of object-oriented programming and the design of SOLID, they show us how useful it can be to have good comments to detect possible irregularities in the practices of these principles.

The semantics within the code

Can be automated the derived merges from refactoring code to different bands? This is one of the objectives of Plastic SCM, trying to give semantic meaning to the changes produced in the code. They assure that they get to deal correctly with 15% changes in the whole code and up to 30% when they focus on unique files. To make it easy, they have started to develop a new tool, much more visual. All an innovation!