So, what's a GitSense context?
You can think of GitSense contexts, as "code change" filters for Git's history and with them, you can control what parts of Git's history, the context user can see.
For example, if you wanted to show others, what is changing in your 2.0 release, you can create
a GitSense context, that only includes relevant branches and file changes for that release. And
by having others view Git's history through that context, you can ensure the changes that they
see, will always be 2.0 relevant.
In a nutshell, GitSense contexts, makes it possible for you to put code changes into context for others. And in this
blog post, we'll highlight some interesting ways, that they can be used, to help reduce information pollution and speed the discovery of information.
Bitbucket, GitHub and GitLab Repos
Need to put repos that are hosted on Bitbucket, GitHub and GitLab into context? No problem.
You can easily combine repos from Bitbucket Cloud/Server, GitHub/GitHub Enterprise and GitLab Cloud/Server.
And in the near future, you'll be able to include repos from Visual Studio Team Services as well.
Click on the link below, to see how you can combine repos from different sources, with a GitSense context.
Use Cases for GitSense Contexts
Here are some interesting ways, that you can use GitSense contexts, to control the flow of information:
For more examples and to learn to how create your own contexts, please refer to the
Quick Introduction to GitSense Contexts Tutorial context.
Deep Integration Support
With Bitbucket Connect, Bitbucket users will soon (early July),
be able to create GitSense contexts for their private repos. And if they want to, search for changes in
GitLab and GitHub repos, all from within Bitbucket.
We are also planning on developing deep integration solutions for GitLab and Visual Studio Team Service as well, so stay tuned for blog updates on that front.
And this brings us to the end of this blog. And as usual, we hope the blog post was informative and that it gave you some ideas on how you can work smarter with GitSense contexts.
General Availability for GitSense Server and Cloud
We are shooting for early July 2016, for general availability for GitSense Server (install on your own infrastructure) and GitSense Cloud (managed by us), so stay tuned for further blog updates.