![]() What I would expect to see here is what Gitkraken displays on other feature branches. ![]() However, Gitkraken appears to think that commit 885da9 and all of its parents also "belong" to the branch "MAG-33." even though "MAG-33." didn't even exist at the time that commit 885da9 or the earlier commits were created. The feature branch starting with "MAG-33." was created during development and should only consist of commit b2b550. In the screenshot above, the commits at the top all "belong" to the "dev" branch (as evidenced by hovering over the commit and observing the branch tag that pops up on the top left). However, I recently found while scrolling through the commit and branch graph in Gitkraken that one of these feature branches seems to have hijacked all of the previous commits from the "dev" branch. Future investments in GitLens will benefit ALL users, free and paid, whether you have an account or not.I follow the standard practice of maintaining a "dev" branch in my software project and adding new features by first creating and checking out a new branch, writing the new feature, then merging the feature branch back into the "dev" branch. With GitLens now being part of the GitKraken family of tools, we’ll be able to evolve GitLens at a faster pace than ever before. This is yet another reason joining GitKraken will help drive innovation for GitLens: there’s so much knowledge and experience within the GitKraken teams after 6+ years of building GitKraken Client, the people at GitKraken really understand Git tooling. The graph will help GitLens users verify recent Git actions on the repo and show who made what code changes and when. We plan to bring powerful visualization features like the GitKraken Client commit history graph to GitLens. What does the future hold for GitLens? We will continue to invest in making the hard-to-use, but powerful features of Git more accessible in VS Code, like merge conflict resolution and comparing the difference between branches, which users are currently only able to visualize in tree view in GitLens. area-plus-account Issues or features related to GitLens+ accounts bug Something isn't working needs-more-info Needs further information, steps, details, etc. We will also not be taking anything away or limiting access to any existing GitLens features, nor will we ever charge for them. Those are the foundational goals of GitLens, and the core features that enable this magic won’t be going anywhere, nor will they stagnate. With better understanding comes greater productivity and better outcomes. So I set out to create an extension to enable VS Code to provide quick insights into that rich history and make it easy to go back in time and see how the code evolved.įast forward to today: GitLens has grown to provide a wide array of tools and visualizations to unlock the untapped knowledge within a repository to help you better understand code. And I never found any good tools to make that process easier and less painful. Throughout my career, I’ve always learned so much from a codebase by diving into its history, especially when trying to fix bugs or evolve legacy code I didn’t understand yet. I had been wanting to do more with TypeScript and decided to try to build a tool to help me and my team be more productive with Git. Once VS Code introduced an extensibility model, I jumped right in. GitKraken also allows code editing directly within an app with its built-in code editor. You can add review comments as necessary to provide feedback. And ever since, I was hooked on creating and building tools to scratch my own itch to make the things I managed better, easier, or faster.įast forward many years, I discovered another Microsoft tool: VS Code, a beautiful, fast, streamlined, just-in-time IDE, and I quickly fell in love. The side-by-side diff view of GitKraken Client makes it easier to see the exact changes made to the code by comparing the files. It became so popular at launch that I effectively launched a DDoS attack on my college network which caused an outage for a day or so. ![]() One of my first apps was a shareware tool to show desktop notifications for POP3 email accounts. I could imagine something and bring that vision to life very quickly. When I first discovered Microsoft Visual Basic, I was hooked. To share a little information about why I created GitLens, let’s start by going all the way back to my very early days as a budding developer.
0 Comments
Leave a Reply. |