Gitkraken Free Version Private Repo

0 views

Skip to first unread message

Eliz Cisneroz

unread,

Aug 3, 2024, 5:13:14 PM8/3/24

to divenlerbma

I've been using GitKraken for a while now, since about May of this year and it never gave me any trouble, except for now.I was working on a school project and GitKraken now prevents me from opening its repository, because, apparently, this is now a Pro feature, although, I have a Github Pro account, which I use to login in Gitkraken, so, I should have access to Pro features, but I don't.

The GitKraken edition page on their website shows that working with private repos is a paid feature of the KitKraken software. Your GitHub Pro account doesn't mean you get GitKraken Pro features. It's a case of different companies with paid software editions both called "Pro", but with their own benefits.

When you sign in with GitHub, GitKraken Desktop will check whether your GitHub account has the GitHub Student Pack. If the app sees the pack, you should see the Pro flag in the bottom right of the UI and you will be able to open private repos.

first of all: - afaik i can use Bitbucket with GIT - is this true?
So, these are some of the major differences. There are prolly several other minor differences that one might realize once you use both of them.
The question is: Which Git GUI should I use with GitHub, Bitbucket or GitLab? A friend of me told me that i should run (use) GitKraken
Gitkraken is told to be a commercial project that only wants to make mone.y
but technically spoken gitkraken has some interesting features.
GitKraken connects to all 3 to clone/add repos, create/view PRs & more. Free for Windows, Mac & Linux!
So the question is: should loook at gitkranken or stay with GIT, Github and Bitucekt
and leave gitkraken as a tiny commeercial project that is not worth looking at

Bitbucket is a Git-based source code repository hosting service owned by Atlassian. Bitbucket offers both commercial plans and free accounts with an unlimited number of private repositories. Bitbucket Cloud (previously known as Bitbucket) is written in Python using the Django web framework. Bitbucket is mostly used for code and code review. Bitbucket supports the following features:

GitLens supercharges your Git experience in VS Code. Maintaining focus is critical, extra time spent context switching or missing context disrupts your flow. GitLens is the ultimate tool for making Git work for you, designed to improve focus, productivity, and collaboration with a powerful set of tools to help you and your team better understand, write, and review code.

GitLens sets itself apart from other Git tools through its deep level of integration, versatility, and ease of use. GitLens sits directly within your editor, reducing context switching and promoting a more efficient workflow. We know Git is hard and strive to make it as easy as possible while also going beyond the basics with rich visualizations and step-by-step guidance and safety, just to name a few.

Quickly glimpse into when, why, and by whom a line or code block was changed. Zero-in on the most important changes and effortlessly navigate through history to gain further insights as to how a file or individual line's code evolved. Visualize code authorship at a glance via Git blame annotations and Git CodeLens. Seamlessly explore Git repositories with the visually-rich Commit Graph. Gain valuable insights via GitLens Inspect, and much more.

Use the rich commit search to find exactly what you're looking for. Its powerful filters allow you to search by a specific commit, message, author, a changed file or files, or even a specific code change. Learn more

Launchpad brings all of your GitHub pull requests into a unified, actionable list to better track work in progress, pending work, reviews, and more. Stay focused and take action on the most important items to keep your team unblocked. Learn more

Easily and securely share code changes with your teammates or other developers by creating a Cloud Patch from your WIP, commit or stash and sharing the generated link. Use Cloud Patches to collaborate early for feedback on direction, approach, and more, to minimize rework and streamline your workflow. Learn more

GitKraken Workspaces allow you to easily group and manage multiple repositories together, accessible from anywhere, streamlining your workflow. Create workspaces just for yourself or share (coming soon in GitLens) them with your team for faster onboarding and better collaboration. Learn more

Quickly see the evolution of a file, including when changes were made, how large they were, and who made them. Use it to quickly find when the most impactful changes were made to a file or who best to talk to about file changes and more.

Easily visualize and configure interactive rebase operations with the intuitive and user-friendly Interactive Rebase Editor. Simply drag & drop to reorder commits and select which ones you want to edit, squash, or drop.

Context switching kills productivity. GitLens not only reveals buried knowledge within your repository, it also brings additional context from issues and pull requests providing you with a wealth of information and insights at your fingertips.

Simplify your workflow and quickly gain insights with automatic linking of issues and pull requests across multiple Git hosting services including GitHub, GitHub Enterprise Pro, GitLab, GitLab Self-Managed Pro, Jira, Gitea, Gerrit, Google Source, Bitbucket, Bitbucket Server, Azure DevOps, and custom servers.

All integrations provide automatic linking, while rich integrations with GitHub, GitLab and Jira offer detailed hover information for autolinks, and correlations between pull requests, branches, and commits, as well as user avatars for added context.

When you're ready to unlock the full potential of GitLens and our DevEx platform and enjoy all the benefits on your privately-hosted repos, consider upgrading to GitLens Pro. With GitLens Pro, you'll gain access to Pro features on privately-hosted repos.

Preview Pro features instantly for free for 3 days without an account, or start a free GitLens Pro trial to get an additional 7 days and gain access to Pro features to experience the full power of GitLens.

With GitLens Pro, you gain access to priority email support from our customer success team, ensuring higher priority and faster response times. Custom onboarding and training are also available to help you and your team quickly get up and running with a GitLens Pro plan.

Contributions to the documentation are greatly appreciated. If you find any areas that can be improved or have suggestions for new documentation, you can submit them as pull requests to the GitLens Docs repository.

What @Ryiah said. If I were rolling my own solution, it would be SVN, not Git. SVN handles big binary files much-much better than Git, easier to use, basically more suited for game development in general.
I would probably set up an SVN server and back it up into a remote repo or just back it up into the cloud on any way.

Self hosted CollabNet Subversion Edge with Active Directory authentication. Not an indie developer, tho. We do many projects in parallel for different customers and need to be able to set up different levels of access privileges in our repos. Also, binary files galore as source art files go into the repo as well.

Using perforce its definetly overkill in my case, but its interesting to hear that some companies use it.
If my project grows and i would have additional participants , then i probably will use the cloud Unity services, it makes a lot of sense and i dont get myself in the situation of the weak link , because then if something goes wrong on my side it would effect others workflow.
So in that case it is actually make sense to deploy the sourcecode to Unity cloud service.
Then for team members it would be easy to share the contributed work between each other.

Its very interesting observation, but i try to do the best of it, so anyone who is in my situation here you go you have choices, but you should consider following: think and plan for grow and structure your project so that you wouldnt be stuck at some point of time!
Wish me luck, i hope that i pretty quickly would be able to setup a SVN server and push the code to it.

In every company I have worked at other than 1 we used git + git lfs. I have never had issues with large binary files etc, but thats because you are meant to use lfs if you want to use git with projects like unity projects.

So if no lfs, go with SVN, otherwise git + lfs is just as good as SVN but you get differences in what you can and cant do. I prefer git but if your comparing SVN to git with lfs, its basically personal preference at that point as they are both ample for the task.

I use SVN, on a home brew linux box. I have dynamic DNS already pointing to my home IP for reasons of running a game test server, which also works nicely with the SVN server allowing me to access it anywhere at basically no cost for my version control with no project size limits.

The one constant is git is not good at managing a lot of binary stuff. And distributed VCS for managing binary files can easily kill productivity. This is an area where it gets progressively worse with scale and will at some point become untenable.

I find myself programming and checking in far more frequently and with a larger number of file changes than I do editing large binary files for art and audio assets, etc. The repo for my code is significantly less than half of the data repo, and as more content is created, that ratio becomes far smaller.