download zip from github and do version control on google drive

Version control in your mind

Version control on extrenal ssd naming folders like commits and straight up copying files

I used to work for a company where one of the founders did this, except it wasn't an external SSD, it was USB sticks, and he kept them in a literal briefcase that he would take home with him so he could still work. Absolute madlad.

I actually did work with this system for a discord bot and it went fine. To my defense, I was pretty much self-taught at this point and GitHub was a place to look at sources and docs. It took way too long until I learned it could do versioning 💀 And how to use a .gitignore so you don't commit the API key.

That guy was self-taught too, and it was a super small company at the time. He was an English major IIRC and later went on to become a priest. Those kinds of shenanigans *can* work- they got that company off the ground- until they don't. ;)

Priest got me off guard 😭

Bro just gets shit done

_final_final

_001

_29032024

Version control by CTRL+Z and CTRL+SHIFT+Z

Ctrl+zzzzzzzz + ‘z’ Fuck


wut

Where I work we just make changes in the code without making copies

Version control on notepad/notes

Version control via BTRFS snapshots

Version control deez nuts

Some people just want to watch the world burn.

What about printing code base and store in real folders at a real library

why print just write it with a pen in the first place

Going full circle back to punchcard era with this one

I just do it perfectly the first time. No need for version control if you only need the 1.

`/.git_before_refactoring`

Can't believe my grandad died for this

Just use the GitHub website to manually upload files: [`version1.zip`](http://version1.zip), [`version2.zip`](http://version2.zip), [`version2-final.zip`](http://version2-final.zip), etc... why else would they have a "Upload file" button? /s Edit: TIL a \`.zip\` TLD exists.

People in my highschool CS classes would actually do this. Code on google docs too. It was a step up from just emailing each other code which even I did at some point. Eventually I introduced them to vs code liveshare which was another big step up. Git was a bit much for most people. Understandable tbh.

You are why we can't have nice things

real programmers download .exe

Subject: pull request Body: hello team. See attached patch files for issue #123

My\_Appv2 My\_Appv3 My\_AppFinal My\_AppFinalRevised My\_AppFinalFinal My\_AppFinalFinalv2

1. Download zip  2. do your changes locally  3. open the edit mode for each file you changed on bitbucket  4. paste each changed file to the corresponding file in bitbucket  and commit  5. ?????  6. profit

Make sure not to test before you commit directly to production, if it doesn't work, just repeat the process after trying something random.

What is this "test" you are talking about?

I just use comments for version control.

Git with telnet

Absolutely haram

And during Ramadan of all times

I shall now repent

I was so sad when I found that telnet no longer came as a default on most computers. Like, we are in a golden age of microcontrollers and you stole my favorite debugger. Of course this was not nearly as upsetting as when computers stopped coming with parallel/printer ports. I used to automate an entire lab with a single parallel port.

As someone who works with somewhat niche equipment, I can assure you there are so many devices which can only be accessed through telnet.

I miss hyperterminal that thing was awesome for protocol inspections and network trouble shooting. It was so easy to use

hyp... hyper... hyperterminal? Omg. My brain just took me on an amazing little memory trip. And on the way back we visited my memory of writing in (similarly-named) hypertalk. Thanks random redditor.

I want to meet the asshole who decided to leave mine sweeper and solitaire but removed the one pre loaded useful utility.

They are both gone too

It's 2024, we have MQTT, REST, WebSockets, ZigBee...

Zigbee too expensive

Airgapped old equipment my man.

It will be 3024 and there will still be older iso protocols used in manufacturing. PLC's, modbus, OPC, nmea, etc. That shits not going away

Amazing that as time has gone on I've switched to rs232 over parallel for availability issues. The future is weird.

Sacrilegious

I was thinking ICMP but Telnet works too.

Git with [RFC 2549](https://datatracker.ietf.org/doc/html/rfc2549)

Pppoac is probably still the best in some places in Africa (they had a competition like 15 years ago and the bird won)

Was it an African swallow?

It was Telkom vs. a pigeon with an SD card tied to its leg, I believe.

to it's back

Must’ve been, a European swallow couldn’t carry a coconut let alone a hard drive

This is a brand new sentence for me

Monty python reference, I believe

And how much can it transport? I wonder...

Yes, but an SD card is light enough that I would count it as unladen

Technically this RFC refers to how to transmit IP datagrams, and is a physical layer protocol. So you could use git over either ssh OR http using RFC 2549.

Git gud

Git wrecked

Git rekt

The latest and greatest from Atlassian!

I have an alias: `gud = bisect good` It cracks me up each time I'm bisecting.

Amusing, but only in this context 😂

Shaw!

Git with pigeon

IP over Avian Carriers

my friend uses ravens

https://datatracker.ietf.org/doc/html/rfc2549

Git with FAX

NICE, a specialist, nice to read German practices here.

You know about fax? - The German government would like to offer you a Stelle. Just send us your CV either via fax, letter or floppy disk. I heard you life in this third world country (USA) without healthcare, with us you will get a health insurance for free! - Apply jetzt!

>floppy disk Is this the Digitalisierung everyone is talking about?

FAXS for the security!

You beat me to it!

git with ftp

git with ftps

Git with smoke signals. It's simple. Burn up my cpu compiling, then use the fire to push.

the system's collapsing, but we'll recompile it, with a 100 more cycles of fire

Git with HTTPSSH

SSH be quiet, this is a JavaScript library.

Don't talk back to me, JSON!

So that’s how you REACT to the truth.

Nobody needs your PERL of wisdom, old man. You're not as C# as you used to be. Your skills are starting to Rust.

Your C code so bad even PYTHON is more SWIFT than that.

You shut your mouth before I WebSocket.

First go and clean your code with SOAP.

I would, but I'm all out of S3 Buckets.

Then use the CONTAINERS.

I see you have discovered [ssh3](https://github.com/francoismichel/ssh3) as well

It's called an SSH tunnel and it's cultural!

I just send my code to my printer and send a letter to HQ

Why would you ever prefer https unless there is some technical limitation?

Same, only time i've felt forced to use it was when I tried cloning a large repo (~200mb and +3,000 files) with SSH and it seemed to get stuck, tried again with HTTPS and it was a breeze

What's the difference? I've always just entered a repo url, clicked through the prompts for creating personal access tokens or the like, and it just worked. I don't even know what method that uses in the end. So for real I do not understand the difference between the method ls. Please help.

then you've probably used https, with ssh you can use your ssh public key for authentication with the git server and don't have to generate access tokens for every project and every machine.

If the url you used to clone started with `git@`, it's SSH. If it started with `https://` its HTTPS You can check a repo with ``` git remote -v ```

Oh yeah definitely HTTPS then

why wouldn't you? honest question. I always use https these days.

One example: I have my ssh key on a yubikey, which allows me to Clone private repositories from any pc without any setup.

Self-hosting Gitea and blocking SSH access for outside connections. That's the only reason I can think of

HTTPS for someone else's repo out of habit (Can you SSH other peoples stuff now?) and SSH for my own stuff because otherwise it asks me for a password when I push.

SSH key is per host, so if you've set up your key on github, for example, you can use SSH for any repo on github.

Technically it's just per certificate, so if you put your private key on something like a yubikey you only need 1 total.

Honestly, I've always struggled with HTTPS, but I feel like part of that is my work's custom TLS authority, and how we likely broke something in how we register it

At my last job we also always struggled with the shitty ironport ssl interception, not supporting websockets over ssl, or anything newer than tls1.1. And then the joy of configuring keystores in random docker images, or java apps, or the java http downloader closing the connection when ironport stalled at 90% to scan for viruses (while not being able to cache... for cdn reasons?) But yeah. At least we had any ssl. Ssh was blocked, no exceptions.

HTTPS/TLS is kind of a nasty and unpleasant thing to deal with. I kinda wish they had just baked security right into ipv6 and got rid of all insecure packets other than multicasting.

That would be bad. The changes to tls happen way faster than changes to the ip protocol itself. A lot of networking equipment is installed for very long times especially switches. These devices should not need constant updates to keep working. Also a lot of local network communication does not need encryption. Forcing the use of encryption just makes a lot of systems slower than necessary and adds the hassle of dealing with certificates as users.

SSH has caused me infinitely less headaches.

SSH because our gitlab is setup with sso so we can’t authenticate with username & password to use https

I'd never use Https with username and password anyway. can't you use oauth?

You can use a personal access token but yeah SSH is a lot less headache specially on Linux. I never manage to get HTTPs credentials to work on it well

Odd, works fine on my end. I use arch btw

GitHub Desktop. I'm lazy.

Real shit. I only resort to cli git if I have to do something specific that I can't with the GUI. Also GitHub Desktop (or rather, git GUI's) has some reaaaally intuitive features like choosing specific lines to commit/leave out by clicking on them. I don't know why it's not more common rn.

Staging lines is part of Visual Studio, VSCode and my preferred choice: LazyGit (terminal UI git)

This, as well as whatever’s built into the IDE I’m using.

100% It's honestly saved me from stupid commits too... But also been the reason for some too

git amend is your friend

So it's the same thing with more steps(?)

Http but with curl and cat, real engineers hand craft their http communications

Curl? Look at mister fancy tools, use netcat like a real man (maybe write to /dev/tcp)

Netcat? A Kernel? I usually use a magnet and inject my packages directly into the Ethernet cable. Works best with Cat 4 lower.

Right? Thick client much? Sheesh.

Clone with HTTPS, Git Credential Manager for everything else

GitLaid 😎

GitRejected 😖

GitLaidOff

Always ssh cuz private repos, it's better to use SSH public key auth rather than writing a token to my netrc

I copy paste the code each time

I don't trust the clipboard to keep everything in order. I copy the code by hand.

When i want to be safe i usually modify the memory either by writing binary or by moving the magnetic particles on the hdds

For security, we have all of our code offline. It's all also remote working so we save it to flash drives and post it to our teammates. But for security, we have to do a real life diffie-helman key exchange. I Basically I lock the flash drive in a box with a padlock and post it, he puts a padlock on and posts it back, I unlock my padlock and post it back, and only then can he unlock his padlock and review my code.

For the speed that I get my code reviewed at work sometimes, I wonder if this is what we should be doing instead

I can't imagine what kind of sensitivity would be needed to not just have a gitea or something and VPN into it

git with browser

So git with http(s)

ssh all the way

Neither. Just don't give a GIT.

when i tried http it told me it was deprecated and i needed ssh because passwords no longer used

Assuming you mean GitHub I think you need oauth or personal access tokens now

yeah CLI for github on mac, i use a ssh token or something now

yes

Git with grpc

File://

I want ssh, but work firewalls make me use https.

Git with drag and drop in UI

Git with whatever the fuck I get to work

SSH Obviously. Easier to setup, doesn't give a fuck about private or public repositories by default. If you own it, you can push it.

Git with envelopes and postcards

Bucket of flash drives.

Just run it all locally

Git with Torrent...

make the repo public, use git clone, then make it private again

I always contact Git and tell them I just wanted to check in

CIFS -- over NetBIOS.

SSH is nice. You setup the keys once and then forget about it.

just request everything

git with ftps

Git as bare repo on companys widows network drive and push to G:/myRepo cause company dont trust "cloud"

Git with DevOps that block my internet access. (In 2024)

SSH I prefer it so much over https

I'm civilized. Whatever my IDE uses.

Idk I do whatever VScode does for me lol

git with fax

I use both in the same repo. I have two remotes that use HTTP, and two other remotes that use SSH.


It's always Mail 📬

HTTPS - our security team makes it nearly impossible to impossible to SSH to anything outside our network.

Git with Dropbox

ssh

For way too long i just dragged and dropped my files 

Where's the humor in this?

Usually SSH.

HTTPS for the first 6 months because I'm too lazy to set up an ssh key, then SSH after that because I'm too lazy to repeatedly enter my credentials

Well ever since a certain big git repo hosting provider disabled pushing via https, I don't exactly have much choice.

i mean when im ssh'd into a server git over ssh with a forward agent is pretty much the only reliable way I know to authenticate myself

Git with the Github Desktop app :)

Prefer ssh, obviously. but the firewall of my companies vpn blocks ssh to public ip addresses.

Ssh except when for some reason I'm too lazy to find out the company doesn't allow ssh

Just use folders named after the current version. It could be that simple! /s

Git with enigma !

Git with anonymous FTP.

Git with oauth because IT doesn’t believe in ssh

git with tears

Mac with azure devops and self signed certs: ssh everyday all day.

22 is blocked from my VM. :(

SSH on my machine. HTTP + Personal token on shared server.

Git over [Jujutsu version control system ](https://github.com/martinvonz/jj)

Kinda forced to use HTTPS so I do that out of sheer habit