Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
JhonDoe28225y@JoshBent I second that. rather easy steps in git kraken. although I don't use it that often, I prefer git bash in windows(I'm a cli user most of the time). haven't had any problem with that.
-
@JoshBent Also, it forces all devs to install gitkraken. I want to keep dev environment as close as possible to native installation without added components.
So far only 3 are required :
WebCompiler (SASS plugin)
GitHub
AzureDevops nuget sources
But I’ll definitlly take a closer look ! Seems like a very nice toy -
@JoshBent Oh, just looked at pricing. Way to expensive for small company. I guess we'll pass
-
@NoToJavaScript there's many other GUIs for git, that make it as easy, just gitkraken is the best candy out there.
-
@NoToJavaScript btw indeed I forgot their pricing for companies, I enjoy it for much less premium.
-
Gitkraken is electron-based.
They did not remove some debug menu they use internally.
Just leaving this here: asar.
(you should pay if you happen to like the sftware tho) -
gitext works for me. plus a couple of custom scripts bc my boss is a Makefile maniac....
-
@Cultist the "debug menu" aka dev tools is in all electron / chrome apps and can be forced even if you iirc deactivate it
you don't have to pay it either, it is just going to prompt rarely "this seems like a private repo, are you using this for non commercial purposes?" and fuck off, though I like giving back to such outstanding piece of kit -
@JoshBent I'm not talking about the builtin electron dev tools.
I'm being vague on purpose. As I don't want to make them lose potential customers.
Even without a forgotten debug menu, electron apps paywalls are easy to bypass. Such a bad choice for commercial software. -
@Cultist ah I think I know what you mean now, nevermind.
But either way, patching out most software paywalls is easy to begin with, no matter the base (most often just literally a DBG JMP because they all use the same library that does it on prefetch), as they don't do anti tamper signature checks or obfuscation well and even if they do with some custom VM like e.g. koiVM, it can still be reversed and or locally emulated if it is phoning home for certain parts of the software.
I hate Pull request system!
Plot twist: I just put it in place in my organization because I see the benefit.
Just spent 4 hours (Note : delay was because git refuses to write to stdout and writes everything in sdterr. And couple other things) developing a helper “powershell” script for “small tasks”. It sits directly in the project and as of 30 mins ago available to all devs.
Let’s say you need to change a typo.
Normal process:
• Create a branch
• Fix problem
• Commit/push
• Create pull request (This one was NOT easy. I’ll explain why if someone is interested)
• Switch back to master to fix second bug
Script does exactly that now. ./CreatePullRequest.ps1 <tmpbranchname> <Comment>. (The target for pull request will be the original branch, not limited to master)
Now I’m trying to find what I missed. Because I missed something, 100% guarantied.
rant
prsarebad