Search Results for "vs code"

GitLens, part of GitKraken’s legendary Git tools, is an open-source extension for Visual Studio Code. GitLens supercharges Git inside VS Code and unlocks untapped knowledge within each repository. It helps you to visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more.

git-flow-next is a branching model and a set of command-line extensions tailored to enforce that branching model for Git repositories. The underlying workflow was first described in 2010 and is designed around two long-lived branches (master (or main) for production-ready code, and develop for integration) and multiple supporting short-lived branches (feature, release, hotfix) for day-to-day development. With git-flow, each type of branch has explicit purpose and merge rules: features merge...

...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.

...It lets users inspect how a file changed over time by replacing a supported repository URL with the Git History domain. The tool works with GitHub, GitLab, and Bitbucket file URLs, making it useful across several common code-hosting platforms. It presents changes as an animated, readable timeline instead of requiring users to manually step through commits. The project also offers browser extensions, a bookmarklet, a CLI, and a VS Code extension for different workflows. Git History is especially useful for developers who want to understand the evolution of code, documentation, or configuration files quickly.

...It also supports “pkgsets” (similar to virtual environments) so you can maintain isolated sets of Go package dependencies associated with specific Go versions or projects. gvm caches cleaned source copies to speed up repeated installs and helps keep your Go workspace clean. Developers use it especially when working on projects that require different Go versions (e.g. legacy code vs bleeding-edge) or when testing compatibility across releases. Because it handles both version switching and package isolation, it simplifies the friction of juggling multiple Go toolchains on the same machine.