Do not enable Cloud Patches by default
As our code is not allowed to leave our own infrastructure, the Cloud Patches feature violates this. As it may also violate legal compliance, it should be an opt-in feature only, not an explicit opt-out.
Comments: 20
-
04 Jan, '24
MatveiCloud Patches is a dangerous feature that could exfiltrate private source code that should be off by default.
23
It's also a proprietary, centralized, opaque "collaboration" feature that goes against the Git philosophy. Not impressed. -
09 Jul, '24
Lance StephensPiggy backing off of this with the newest release (v10.1.0) at the time of writing, not a fan of the new Cloud Patch button "Create a Cloud Patch from staged files" taking up valuable real estate between Staged Files and Commit Message.
32
Understand even with an annual subscription you all need to have additional revenue streams, but at the least there should be an option — perhaps next to "Hide Launchpad in status bar" under "UI Customization" — to toggle this off.
This is the desktop app equivalent of making an unwanted browser extension highly visible and enabled by default (cf. Pocket and Firefox.)
Love GitKraken, but it's mission creep "features" like this that turn into death by a thousand cuts. -
10 Jul, '24
Iain ShepherdI'm here because of the new issue mentioned by Lance Stephens above:
22
The [Create a Cloud Patch from staged files] button that's permanently highlighted in the commit pane.
It is obnoxious, Please provide an option to hide this.
(Also this pane was already tight for vertical space, don't want to lose any)
Cloud Patches will require me to navigate a vendor review process at my company and there's just no way I'm doing this as ~noone else at the company even uses GK.
Be grateful that you are getting the recurring license fee. Don't be greedy for extra seats and upsell. -
10 Jul, '24
DaveI completely agree with the above.
14
I use GK mainly for personal projects and my own private source code management. I will never create a Cloud Patch, since the only person I would share my code with is me.
The advertising button is very intrusive. What's wrong with the "drop up" arrow in the green commit button? Couldn't you create your button there and introduce it somehow at first run?
Please, do not force paying users to see ads like this all the time!
Thanks -
11 Jul, '24
CCI was happy to ignore all the bloatware you've added over the years, but this "Create a Cloud Patch" button right above the message box is really something else. Please reconsider if it's worthwhile to antagonize your paying customers in an attempt to upsell whatever this is. I know it's having the opposite effect on me.
16 -
11 Jul, '24
ValentinoThe new button "Create a Cloud Patch from all files" is very intrusive
14
I'm personally not interested to use cloud patch features.
It would be helpful if we had the option to hide this button or disable the cloud patch features.
Furthermore, in our enterprise, there are restrictions against using cloud services. -
11 Jul, '24
Barry NewtonThe moment Security Department notices this button, GitKraken will be banned from my company forever. What a terrible idea.
11 -
12 Jul, '24
AndreEvery other UX change made to Gitkraken over the years (I've been subscribing since 2017) has been either a positive change or one which I haven't noticed. This is the first change I've seen which forces me to think about a feature I don't want or need every time I make a commit - needless to say this is extremely annoying.
8
If you could provide an option to turn off Cloud Patches that would be much appreciated. -
15 Jul, '24
Axel HeiderPlease allow removing/disabling this. It bloats the UI and and the feature itself is dangerous, as sharing with "the cloud" is a no-go for commercial work environment.s
6 -
16 Jul, '24
TwoleelandEvery time you introduce new features like this one with the button, you should make them configurable and not force them!!! 😉
7 -
17 Jul, '24
LauraI haven't found the time yet to explore what cloud patch is, and it may be awesome, but I'd rather it be an opt-in feature. I rely on my gitkraken workflow and need a calm simple UI. I do not want to experience distraction at the moment of making a commit.
7 -
17 Jul, '24
Steven FirthThis is purely to sell a feature most people wouldn't want. You've used bold font to make it stand out and this has no legitimate purpose, you are taking a liberty and advertising.
6
This should be removable from the UI along with anything else that isn't a core git function. -
22 Jul, '24
AdiFully agree with the other comments. I don't mind the feature, but none of my colleagues are using GK so it is not helpful for me.
1
The new button is highlighted and right in the area of GK you use the most and is most cramped as is. There is already shortage of vertical space there.
If GK really doesn't want to disable this by default, then put it on the top menu or the right-click menu similar to stash/discard. -
22 Jul, '24
Bryan FarrellAgree with all other comments. This feature should not be enabled by default and should only show up in the UI if you choose to use it.
2
Furthermore, the option to enable or disable Cloud Patch should be set during an install by an admin of the computer. My company has strict rules about code exposure outside the organization, and even being able to turn it on or off from the setting is not enough, as if a non-admin of the box can reenable it, then they can create a link that allows anyone with the link to view the code.
My security department is hesitant to allow GitKraken usage on any larger scale with a dangerous option like this in the application, especially when you push it on people like you have with its intrusive button.
I hope you consider all of our concerns. As others have said, your going to loose a lot of enterprise business adding a feature with such high security risks without an option to disable it easily.
I hope you take all our concerns seriously. -
23 Jul, '24
James BlandfordAbsolutely. Adding Cloud Patches is a neat idea, but please can we opt-in/out? I'm in the same position: our enterprise would fire me instantly if I were to upload code to a remote server (even if it's secured!)
1 -
29 Jul, '24
DanielMy beef with this feature is that the button is too intrusive. Every time I make a commit my eyes go to that button and read its text. For whatever reason my brain refuses to filter it out(probably because the button is highlighted, brighter then the surrounding).
Please move that button somewhere else or blend it with the surroundings so if I don't need it my focus is not diverted to it.
I'm finding myself getting irritated with every commit because of it. It got me to the point of writing you an email about it and being redirected to put the comment here. And I rarely bother with that kind of stuff. -
30 Jul, '24
Roman MergedThere's not all that much vertical space available in the sidebar. Certainly not enough to justify a permanent button for this feature. It's not like cloud patches are in everyone's commit workflow. Some people (most?) will never click it once. Please give us a way to hide it.
-
30 Jul, '24
Chris Bowie Admin"Hide "Create a cloud patch from all files" because it takes up precious vertical space" (suggested by <Hidden> on 2024-07-30), including upvotes (1) and comments (0), was merged into this suggestion.
-
31 Jul, '24
NeilPlease make this opt-out. It is a feature I will never use (due to corporate policies and personal reasons).
There is so little vertical space there anyway. -
08 Aug, '24
CCWhile not an option to completely disable, the changes in 10.2.0 to the commit area are a decent compromise and fix my biggest gripe with cloud patches. I appreciate that our feedback was taken into account.