This looks like good CLI UI for git, something that git needed from day one.
Bit – A modernized Git CLI written in Go
81–90 of 132 posts
Re: Bit – A modernized Git CLI written in Go
#82Earlier quoted context omitted.
- rant mode on Having used most SCM since RCS days, I get to differ, but since I am left without another option, so just like with C and JavaScript, I suck it up and get the job done by whatever means. - rant mode off Thanks for bringing a bit more of security into the IT world with a Go version though.
Why would a different CLI (presumably still using libgit2) improve security? Especially if it's installed like this: curl -sf https://gobinaries.com/chriswalz/bit | sh;
> Especially if it's installed like this: curl -sf https://gobinaries.com/chriswalz/bit | sh
What's wrong with this? It's no worse than git clone && make
or any of the other hundred incantations of executing code from the web.
Re: Bit – A modernized Git CLI written in Go
#83Earlier quoted context omitted.
Point being, they are not the same. There is one hour difference between UK Time, GMT and UTC for half of the year, due to daylight saving time.
GMT stays the same throughout the year. The UK switches to BST for the summer. https://en.wikipedia.org/wiki/British_Summer_Time
Crazy enough your statement is equally right and wrong. There is really a lot of confusion between GMT, BST, UK time and Greenwich time. ^^
Greenwich is a borough in East London, there is an old museum with the line on the ground that defined the meridian. You can visit if you come across London.
GMT, namely Greenwich Meridian Time is not actually the time of the meridian of Greenwich for half of the year. When you find yourself working with GMT, you really need to think about how you got there because it's wrong. 90% of the time you meant to use UTC and the other 10% you meant Europe/London timezone.
Re: Bit – A modernized Git CLI written in Go
#84Re: Bit – A modernized Git CLI written in Go
#85Earlier quoted context omitted.
The save command also accepts the commit message on command line only instead of opening an editor. I do not understand how people can live with only a single line for the commit message. For a new feature, I need to provide some details what is added and how it can be used. For a bugfix, a single line is rarely enough to describe the problem, what you changed, and why this change solves the problem. Writing good com…
My team doesn't write long format commit messages and it's never been an issue. When we need to track down changes we use the corresponding mr, which includes a description as well as a link to the relevant cards. I personally like this format more because it lets you both be "dirty" in your branch writing commits for yourself, and not have to use amends/rebasing. I can see how it would be annoying for someone that d…
If you ever switch from Gitlab to another git host, you’ll lose all that history though. Maybe you’re fine with that, but I wouldn’t be.
Re: Bit – A modernized Git CLI written in Go
#86Earlier quoted context omitted.
GMT stays the same throughout the year. The UK switches to BST for the summer. https://en.wikipedia.org/wiki/British_Summer_Time
Crazy enough your statement is equally right and wrong. There is really a lot of confusion between GMT, BST, UK time and Greenwich time. ^^ Greenwich is a borough in East London, there is an old museum with the line on the ground that defined the meridian. You can visit if you come across London. GMT, namely Greenwich Meridian Time is not actually the time of the meridian of Greenwich for half of the year. When you f…
I don't understand why his statement was wrong. GMT does not change according to daylight savings time as far as I know?
Re: Bit – A modernized Git CLI written in Go
#87Earlier quoted context omitted.
GMT stays the same throughout the year. The UK switches to BST for the summer. https://en.wikipedia.org/wiki/British_Summer_Time
Crazy enough your statement is equally right and wrong. There is really a lot of confusion between GMT, BST, UK time and Greenwich time. ^^ Greenwich is a borough in East London, there is an old museum with the line on the ground that defined the meridian. You can visit if you come across London. GMT, namely Greenwich Meridian Time is not actually the time of the meridian of Greenwich for half of the year. When you f…
They weren't wrong at all; they were right.
I suspect you are the one who is confused: the UK is on BST in the summer, and GMT in the winter. GMT is identical to UTC to the nearest second. GMT is not defined as "the current time in Greenwich", and I suspect your confusion is because you think it's "Greenwich Meridian Time". It's actually "Greenwich Mean Time".
The maritime museum at Greenwich is pretty cool though, as is the old observatory. You can see Harrison's clocks there.
Re: Bit – A modernized Git CLI written in Go
#88Earlier quoted context omitted.
Crazy enough your statement is equally right and wrong. There is really a lot of confusion between GMT, BST, UK time and Greenwich time. ^^ Greenwich is a borough in East London, there is an old museum with the line on the ground that defined the meridian. You can visit if you come across London. GMT, namely Greenwich Meridian Time is not actually the time of the meridian of Greenwich for half of the year. When you f…
I don't understand why his statement was wrong. GMT does not change according to daylight savings time as far as I know?
GMT = Greenwich Meridian Time
The time at the greenwich meridian = not GMT
See the problem here? I know it sounds like a bad pun but it's a real problem that every developer in the UK struggled with. To make thing worse, Greenwich the location is right next to the financial district of London where thousands of developers make financial software that are one hour wrong.
Re: Bit – A modernized Git CLI written in Go
#89Earlier quoted context omitted.
My team doesn't write long format commit messages and it's never been an issue. When we need to track down changes we use the corresponding mr, which includes a description as well as a link to the relevant cards. I personally like this format more because it lets you both be "dirty" in your branch writing commits for yourself, and not have to use amends/rebasing. I can see how it would be annoying for someone that d…
If you ever switch from Gitlab to another git host, you’ll lose all that history though. Maybe you’re fine with that, but I wouldn’t be.
Hi, Developer Evangelist at GitLab here.
While we do not want you to leave ... :-) ... you'll have great tools to export your data from projects, for example https://docs.gitlab.com/ee/user/project/settings/import_expo...
Another way is to programmatically work with the REST API and export the needed data (https://docs.gitlab.com/ee/api/). This can be needed to specific backup and persistence routines for data compliance too. I personally recommend to use the Python, Ruby, etc. library bindings for easier API requests.
This won't solve the import into another tool, yet it opens a migration possibility with full access via an API.
Re: Bit – A modernized Git CLI written in Go
#90It’s not mentioned in the README, but is WSL2 on the Windows Terminal app supported? I could run gnome terminal but then I have to configure X11 and that’s a pain. Thanks, this looks awesome.
Incidentally, I've actually found it much less painful to use urvxt through VcXsrv for WSL than anything else. The config at that point is just identical to my linux boxes but it interacts with windows in normal, sane ways and X11 programs generally run just fine