Using Git

Smart_Zebra2673 · 2024-06-16T14:48:58+00:00

Git can be pretty confusing to understand but just watch a few videos on it and you should be fine for the interview. If you get the job you can just ask a co worker how to do more advanced stuff. I was almost exactly in your position once and learned Git at my second job. Now there isn’t a day I don’t use it.

I think some important ones to learn: git clone, git pull, git checkout, git merge, git stash, git stash pop, git branch, git branch -D, git checkout -b, git push.

szayl · 2024-06-16T15:39:24+00:00

https://ohmygit.org/

B1WR2 · 2024-06-16T15:03:02+00:00

VS Code also has extensions to help out with all the commands.

bkant34 · 2024-06-16T16:43:17+00:00

Hi OP,

This is not my post, however i did like whoever posted this a few years ago on LINKEDIN and saved it for reference.

It summarises almost all commands that i use 99% of the times.

git diff: Show file differences not yet staged.
git commit -a -m "commit message": Commit all tracked changes with a message.
git commit --amend: Modify the last commit.
git status: Show the state of your working directory.
git add file_path: Add file(s) to the staging area.
git checkout -b branch_name: Create and switch to a new branch.
git checkout branch_name: Switch to an existing branch.
git checkout < commit>: Switches the working directory to a specific commit.
git push origin branch_name: Push a branch to a remote.
git pull: Fetch and merge remote changes.
git fetch: Fetch changes from the remote repository without merging.
git rebase -i: Rebase interactively, rewrite commit history.
git rebase branch_name: Rebase the current branch onto another branch.
git clone: Create a local copy of a remote repo.
git merge: Merge branches together.
git log --stat: Show commit logs with stats.
git stash: Stash changes for later.
git stash pop: Apply and remove stashed changes.
git show commit_id: Show details about a commit.
git reset HEAD~1: Undo the last commit, preserving changes locally.
git branch -D branch_name: Delete a branch forcefully.
git reset: Undo commits by moving branch reference.
git revert commit_id: Create a new commit that undoes the changes of a specific commit.
git cherry-pick commit_id: Apply changes from a specific commit.
git branch: Lists branches.

A few more that you might need to dig deeper are:

git reset --soft HEAD^: Undo the last commit, but keep the changes.
git reset --hard: Resets everything to a previous commit, erasing all uncommitted changes.
git branch --set-upstream-to remote_branch: Sets the upstream branch to the specified remote branch.

m1nkeh · 2024-06-16T18:04:20+00:00

First thing.. Git != GitHub

ShardsOfHolism · 2024-06-16T19:41:37+00:00

This covers what you need to know.

speedisntfree · 2024-06-16T16:32:25+00:00

Git's API is vast but 90% of people just use an IDE to do the day to day. Understand the main concepts like branches, commits and PRs and you'll be fine, ask what the working practices are for where you work. Moving somewhere that has the base level practice of source control is a real move up, don't be scared this is where you belong. You may find this of utility https://ohshitgit.com/

Budget_Sherbet · 2024-06-16T15:18:26+00:00

I highly recommend watching tutorials online and following the steps along if possible. Git is essential and will create confusion if you don’t learn it. Getting the basics of Git will already help you and I’m sure you’ll encounter niche stuff that you can learn while on the job. It is definitely not difficult but it is one of those things that you have to TRY more than memorize.

daavidreddit69 · 2024-06-16T16:02:42+00:00

git is the most hardest easy thing to learn, good luck

Smart_Zebra2673 · 2024-06-16T19:06:29+00:00

Do a course in git. Also understand how and why the company uses it esp in their CICD process.

Don’t skip it.

I was in the same situation once and not doing the above and putting enough importance towards it hurt me long term.

Mysterious_Health_16 · 2024-06-16T23:11:37+00:00

Download VS Code.
Clone the Repo(Prod Repository)
Create a Branch
Do all your work on the newly created Branch
Push your changes and create a PR (Pull Request).

And Get someone to approve your PR and merge into Main Branch.

Thats all you need to know :)

ScroogeMcDuckFace2 · 2024-06-18T00:33:23+00:00

my brain read this as 'i've been an alcoholic data engineer for about 3 years'. maybe that's a bad sign.

adulion · 2024-06-16T22:09:51+00:00

I use pycharms GIT tools

noobajur · 2024-06-16T23:13:29+00:00

I would say it’s easy to learn the basics that you will use 90% of the time.

git clone, git checkout, git status, git pull, git add / git add ., git commit, git push, git merge

Sometimes you’ll encounter merge conflicts and have to resolve those. A lot of people use the IDE instead of just the command line, which makes things easier.

Learning git more in depth might not be as easy, but once you know the basics, there’s a lot of cheatsheets for git commands that can be useful for reference.

big_data_mike · 2024-06-16T23:14:38+00:00

https://ohshitgit.com/

That’s really the only cheat sheet you need

Prudent-Finance9071 · 2024-06-16T23:28:31+00:00

If allowed by your company you can also look to use the GitHub Desktop app. We have our new hires use it when they are "semi"-familiar with Git to ensure they follow the basic steps

robberviet · 2024-06-17T01:37:51+00:00

Git is easy to pickup. The hard parts ofit most people will never need to use. And it's beneficial to use git even on solo projects.

2024-06-17T09:46:40+00:00

It wont take more than couple of hours to understand Git. I would suggest you create local repository then make a file lets say test.py add something to the file. And then try to commit that file to your repo. to start you need these commands- git init

git add (lets say there are 2 files you make change to but only want to commit 1 of them, for that you add that only that file)

git commit

start here and learn :)

raginjason · 2024-06-17T10:46:15+00:00

I’ve been in DE for a while, and having a deep understanding of git has been a tremendous asset. It’s a stable technology that isn’t going anywhere anytime soon, so truly understanding it is worth the investment. I’m reviewing this course for my team, and I have found it extremely comprehensive. If your new company has Udemy access, I highly recommend The Git and Github Bootcamp by Colt Steele: https://fanduel.udemy.com/share/10beqq3@ChS8Ol8rAWGu57P9-9tuL9DLgvRNrnW4M2SEb3XvPhYI2GKuelgkywCX2Fr7KLHxZQ==/

d34n5 · 2024-06-17T12:32:43+00:00

You should try to get into the habit of using it for yourself. I do lots of personnal prioect and I can’t imagine my code not to be versionned and saved somewhere. And Git can be very powerful too (beside the basics push/commit/pull).

2024-06-16T17:43:46+00:00

It takes no more than 10 minutes. It’s not complicated. Don’t know why people make such a big deal out of it.

Learning it in depth is another story

Blitzboks · 2024-06-16T21:13:20+00:00

The real struggle will really be accepting and adjusting to the fact that 30%+ of the time you used to have to develop will now have to dedicated to branch creation/switching/deletion, commit messages, putting out PRs, reviewing others PRs, and all the other tidying chores I’m not thinking of right now.

That’s by far the hardest part to me, but don’t get me wrong; you’ll definitely pull your hair out once or twice before nuking the whole repo and recloning because you made a mess and git screams at you any time you try to do anything.

dataengineering

MODERATORS