Search Results for "learn"

...Magit looks like a prettified version of what you get after running a few Git commands but in Magit every bit of visible information is also actionable to an extent that goes far beyond what any Git GUI provides and it takes care of automatically refreshing this output when it becomes outdated. In the background Magit just runs Git commands and if you wish you can see what exactly is being run, making it possible for you to learn the git command-line by using Magit. Using Magit for a while will make you a more effective version control user. Magit supports and streamlines the use of Git features that most users and developers of other Git clients apparently thought could not be reasonably mapped to a non-command-line interface.

...Both strategies work well and both have drawbacks as well. splitsh helps use both strategies by providing tools that automatically synchronize a monolithic repository to standalone repositories in real-time. splitsh-lite is a sub-project that provides a faster implementation of the git subtree split command, which helps create standalone repositories for one or more sub-directories of a main repository. If you want to learn more about monorepo vs manyrepos, watch this 4-minute lightning talk I gave at dotScale (or read the slides)... or watch the longer version from DrupalCon. "The Monorepo - Storing your source code has never been so much fun" is also a great resource.

Sourcerer app makes a visual profile from your GitHub and git repositories. Creating your profile is just the first step for us at Sourcerer. Some of the things on our roadmap include engineers to follow and learn from, technology and libraries you should know about, and projects that could use your help. The app looks at repos locally on your machine, and then sends stats to sourcerer.io. The best way to verify is to look at the code. Protobuf messages declared in src/main/proto/sourcerer.proto is a good start as it describes the client-server protocol. ...

Reviewer adds comments on code which developer has to follow up. Useful for managing code quality and determining the quality of work delivered by a developer. Most of all it provides a place where developers can learn from their previous mistakes.