How do you commit in GitHub ?

My personal preference is to git add ... -p. Eyeballing each line as I commit it gives me one last sanity check.

I also like to git commit -v so I can refer to the code whilst writing the commit message.

One thing I do a lot is that I like to create a new branch for even the smallest of changes. If I find I need to further prepare for that change, I can create a new branch from master, make the change then head back to the original new branch and rebase.

I also git reset --hard a lot. And, git commit --fixup ... helps me keep my commits tidy but I know if I'm using it a lot, I'm on my way to a mess.

• Create a useless branch
• Accidentally make it useful
• Really commit to merge the branch to remote master
• Keep calm and merge the pull request to master
• Revert the branch
• Remove the repo
• Repeat.

I start working on a project, when I need to add the first commit I

• git init
• Head over to Gitlab (where I host most my personal work),
• Create a repo copy the remote setting and drop in in terminal
• gitit "some commit message"
• If I want to experiment I create branches

That's it.

I've set gitit to do this:

gitit() {
    git add .
    git commit -a -m "$1"
    git push --all
}

Quick and easy

(I do the same with Github)

Just wanted to wish you good luck on the game jam.

I never really use commit -m. It's personal preference, I guess, but I'm usually either using a GUI front-end for git or feel more comfortable being able to compose it with vim.

Initially start pushing directly to master, but at some point (when the project is out of the "proof of concept" phase) I'll push to a branch. It's a good habit to get into. But, honestly, with a "throw away" project (like a game jam) I would probably just stick with master.

gitkraken. 'nuff said.

New project:

• Create repo on GitHub
• git clone <link to my repo>

If working on my own stuff, im lazy and just work in master:

• Use VS Code git diff view to double check code
• Add files in VS Code or in terminal using git add . depending on what im doing
• Write and submit commit message in VS Code or git commit -m "my message"
• Always in terminal git push

If im working on an actual project i create a branch before that step:

• git checkout -b "feature/my-branch-name"
• Steps as above
• git push

Although on personal projects im actually lazier than I really let on I have aliased it all so:

• gcm "commit message"
• gp

Make a folder in Dropbox/iCloud/Whatever and init a local repo. Download the minified Phaser and start coding. No npm, no Babel, no baggage.

I do exactly what you've described and have written myself some instructions

Becoming more efficient with the command line

Helen Anderson

#beginners#devtips#github#git

Learning about branching, merging and, at some point contributing to open source, is all on my list of things to learn about.

Create repo on github/gitlab -> git init on local -> create .gitignore
-> git add .gitignore -> git commit -m 'initial commit' -> add remote origin -> push
-> checkout -b develop -> git push origin HEAD -> branch setting on remote (protect/CI etc)
-> checkout -b feature/xxxxxxx -> push origin HEAD -> Pull Request -> SELF REVIEW
-> squash merge -> rebase origin develop -> ..... continue ( ˙꒳​˙ )

If there are coworkers around or it's a presentation, then everything is via terminal so I can maintain my cool hacker status.

Alone at my own station I use Gitkraken pretty much exclusively even if the IDE has Git integrated (as most do...).

Sure git is pretty straightforward and I love me some terminal only action but I love Gitkraken's UI and how everything is super easy to do, update, read and analyse.

Highly recommended it. :)