Git? Snow? (geek, weather, covid-19)

[elainegrey]

We are currently at the point where if the forecast is inches of snow, we think "maybe we will see a flake or two." As i headed to bed last night, there were fat flakes falling occasionally. I think if a cluster of snow crystals found each other to fall together, they could stay cold enough to hit the ground as snow.

Tonight's prediction is 2" of snow. Yeah, right.

So are the grocery shortages supply chain or snow panic, i wonder.

I read the announcement of a late February pub crawl in my town with a sense of wonder. The Omicron case rates shot up so fast: could they come down fast enough in the next four weeks for a pub crawl to seem not insane?

In other wonders, i wonder if the tech folks among us have a guide to using git they like. I am really fuzzy on the different ways my colleagues use it, and i am wondering if i should be using it in my personal data repository more cleverly. I use Visual Studio as my editor these days (since the mac changed permissioning, and i would have to recompile emacs to run it). Is it easy to bob back and forth between branches? Right now i use it like i used code repositories in the 90s. At least my coding is slightly more sophisticated than my Fortran coding was, but not by much.

(Feeling like a brontosaurus.)

Comments

[altamira16]

You know, I am looking for the good git tutorials, and I am not finding them. Here is one of the standard cheatsheets.

Yes, it is easy to bob back and forth between branches.

Branches in git can be way more ephemeral than they were in code repositories in the 1990s.

That means in a typical work day, I am going to go to the develop branch, and do a

git pull

to make sure that I am up-to-date with all the changes my colleagues made yesterday.

Now that I am up-to-date, I am going to do

git checkout -b feature/my_new_branch

That means, I am checking out a new branch called "feature/my_new_branch"

Then, I will muck about on my branch.

When I am done with the mucking about part, I will do

git add .

which will stage all the files I created and prepare them for upload. The "." means "add all the files." I can choose to add some of the files instead, but usually I add them all.

Then I will

git commit -m "Ooh boy, I changed the thingamabob"

This will attach a short message to the staged things.

Then I will

git push

which will send the things to github.

That will only send them if my branch exists on github and all that. If it fails because the branch does not exist on github, it gives you a helpful message to make your branch exist on github. I created a shortcut for the command so I don't remember what it is.

Once on github, I will go to the "Pull requests" tab, and it will say, "Hey, it looks like you uploaded a branch, do you want to do a pull request with that" or something to that effect. I will tell it yes, and then there is a template where my coworkers say, "Explain yourself. What did you do, why did you do it? Do you have a pretty picture?"

Then continuous integration stuff runs. Theses are style checks and code tests. If this fails, I will know how to fix it, or I will say "Help me, this failed in a weird way."

Once it passes all that and the coworkers approve of my nonsense, I do a squash and merge. That means all the things I did get squashed down into one commit and merged into the develop branch.

Some parts of this will be completely irrelevant to you, but that is typically how I use git in my work day.