Wife: commit, and come to bed..
Me:
> git commit -m "wife wants me to go to bed"
> git push origin master -f

Oh boy look at the time. It's already screw-up o' clock.

git push --force origin master

$ git push --force origin master

Probably posted before, still funny!

alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'

git add *
git commit -am "stuff"
git push -f origin master

No regrets

Some how somebody managed to fill our repo with the following branches:
Origin/master
Origin/origin/master
Origin/origin/origin/master
Origin/origin/origin/origin/master

What's your favorite shell alias that you made for yourself?

I use this one all the time:

squash () {
git rebase -i HEAD~${1}
}

Runner up though is `git-fuckit` which resets everything to origin/master.

When I first started using Git, I didn't understand the purpose of the 'commit message' and branches.

So I automated the 'git add .', 'git commit -m "update"' and 'git push origin master' so I could update my git repo faster, with one command 😂

`git push origin master --force`

When there is a conflict, a jedi uses the force!

git push -f 😂

*about to push an experimental block of code*

my brain:
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it
don’t do it

Me: “git push -u origin master”

git push --force origin master

```
Your branch is behind 'origin/master' by 562 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
```

`$ git pull`

```
251 files changed, 103274 insertions(+), 1361 deletions(-)
```
okay fuck.

git push origin master --force

Method 1:
1. Read others' people answers on wk70
2. Apply
3. ???
4. Profit
Method 2:
1. cd <ProjectName>
2. git init
3. dotnet new sln
4. dotnet new console #or webapi/lib
5. code .
6. git commit -m "Initial commit"
7. git remote add origin <github link>
8. git push origin master -u
9. profit

It is time. I have to admit it.

I don't understand Git.

I just memorized some basic commands: git commit, git push, git push -u origin master, git clone, git checkout [-B], git merge. That's it, that's the full list. I use them like they're some kind of magic spells that do what I need. Everything else, those intricacies like rebasing, resetting, HEAD and all that shit, is beyond me.

I'm not a real programmer. Real programmers know Git.

git add .
git commit -m "updates"
git push origin master

Race to git push -u origin master

literally every

`git push --force origin master`

> git push origin master

* [new branch] master -> master

Thank you GitHub.

git add -A
git commit -m "fix bunch of shit.'
git push origin master
**98 files changed

hours later
me: omg I forgot to change the hardcoded IP now it's getting 404

git add -A
git commit --amend
git push origin master --force

Enough is enough! I can't do it anymore!

...

alias pm='python manage.py'
alias ga='git add .'
alias gc='git commit -a'
alias gi='git init && touch .gitignore && printf ".idea \n venv \n node_modules \n out \n *.iml \n *.log \n build \n target" > .gitignore'
alias gp='git push'
alias gps='git push --set-upstream origin master'
alias gr='git remote add origin'

...

Much better :D

git push origin master --force

So I am conducting an introductory seminar on git and GitHub for juniors and as per my knowledge I've drafted this outline, please add your inputs..

The seminar will be of 1 day only

1. Install and configure Git and Github

2. Digital Signature mapping

3. Git init

4. New Project with HTML

5. Configure remote (git remote add <origin> <url>) ends with .git

6. Git commit (git commit –m “Title” –m “commit message”)

7. Pushing git push (git remote push origin master)

8. Git commit –amend

9. Git pull (git pull origin master)

10. Git checkout (git checkout –b new_branch_name)

11. Do some changes

12. Git push new branch (git remote push origin new_branch_name)

13. Git switch branch (git checkout <name_of_existing_branch>)

14. Pull requests

15. Git log (git log –oneline –graph)

When a female developer enters:
git push --force origin master

Boss(In company chat): Guys we only need 100 votes to win this award.Do vote and also push your friends and family to vote.
Me: git push -f origin master
Boss: I'll see you tomorrow.
Me: git reset HEAD --hard.

(I think I am gonna get fired)

git push origin master

$ git commit - -amend
$ git push -f origin master

$ git push --force origin master

git push origin ams... backspace, backspace, backspace... master

Long time ago i ranted here, but i have to write this off my chest.

I'm , as some of you know, a "DevOps" guy, but mainly system infrastructure. I'm responsible for deploying a shitload of applications in regular intervals (2 weeks) manually through the pipeline. No CI/CD yet for the vast majority of applications (only 2 applications actually have CI/CD directly into production)

Today, was such a deployment day. We must ensure things like dns and load balancer configurations and tomcat setups and many many things that have to be "standard". And that last word (standard) is where it goes horribly wrong

Every webapp "should" have a decent health , info and status page according to an agreed format.. NOPE, some dev's just do their thing. When bringing the issue up to said dev the (surprisingly standard) answer is "it's always been like that, i'm not going to change". This is a problem for YEARS and nobody, especially "managers" don't take action whatsoever. This makes verification really troublesome.

But that is not the worst part, no no no.

the worst is THIS:

"git push -a origin master"

Oh yes, this is EVERYWHERE, up to the point that, when i said "enough" and protected the master branch of hieradata (puppet CfgMgmt, is a ENC) people lots their shits... Proper gitflow however is apparently something otherworldly.

After reading this back myself there is in fact a LOT more to tell but i already had enough. I'm gonna close down this rant and see what next week comes in.

There is a positive thing though. After next week, the new quarter starts, and i have the authority to change certain aspects... And then, heads WILL roll on the floor.

`git push origin master --force`

When I'm still a beginner in git, I always use git push origin <branch_name> --force, for the sake of pushing my code on the master branch. My co-worker always complain why the hell there's always conflict on the master branch.

Something to cheer you up mid-week:

> alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'

Hmm. This code needs refactoring.
*recodes on Local and uploads*
Works on my branch.
*git push origin master and merge*
Works on Dev.
*deploy to Test*
Works on Test.
*deploy to Live*
Doesn't work.
*compares Live to Test, Dev, and Local*
No f$@%^%%$# difference!?!!

*quits development and lives under a bridge*

touch README, then add README, and commit me, until I can, push to, origin master.

Cleaning up after yourself if so damn important. Even your git repos:

# always be pruning
git fetch -p

# delete your merged branches
git branch --merged | grep -v master | xargs -n 1 git branch -d

# purge remote branches that are merged
git branch -r --merged | grep -v master | sed 's/origin\///' | xargs -n 1 git push --delete origin

In case of Cyclone emergency,
git add *
git commit -m "cyclone times"
git push origin master
Run

When you're clearly in the zone:

Excluding merges, 1 author has pushed 22 commits to master and 22 commits to all branches. On master, 70 files have changed and there have been 16,339 additions and 321 deletions.

I had a small .NET PoC project I wanted to upload to our git server. So added the project to version control using Visual Studio, meaning that VS created a local repository for it. Then I wanted to push it to the remote repository which were created by my colleague. This one was initialized with a commit (.gitignore and Readme.md), so I couldn't push directly. Googled a bit, OK then tried to fetch the remote repo, didn't help. Googled again, tried some "git push origin master whatever" stuff and then rebate, because nothing seemed to help.
OOPS where are my local files? WTF? 😣

Long story short: Experience in other version control systems is not enough or even dangerous when switching over to git. 😂

Share your own useful terminal aliases here:

- grm=git rebase origin master
- gforbm=git fetch origin && git rebase origin master
- vm=vim Makefile
- idea=vim ~/repos/ideas/README.md (where I store all my programming ideas)

git pull origin master --allow-unrelated-histories

Because I like to keep life interesting.

So I made a new GitHub repo and pushed some changes to it, but they didn’t show up. Then I noticed that there are two branches to my project— main and master. And my changes were pushed to the master (coz I did git push origin master) and the default name is now configured to main. So this is what some of you guys were irritated about— changing words like master-slave to primary-secondary for political correctness and all.

Git push -u origin/master --force

That feeling when you've been on holidays for 15 days and the `$git pull origin master` take hours...

Git :- Push rejected. Merge or Rebase?

Me :- git push -f origin master.

git push origin master

git push origin master --force

Is it just me, or does anyone else find it extremely satisfying completing a successful git push -u origin master?

You'll have less of a work to do the following week if you
git push origin master --force
on Fridays

3 months old branch! And I have to resume work on it! git pull origin master ….. fuck me!!

Love it when the maintainer of an open source project you contribute to runs a linter over the whole codebase and force pushes the changes to origin master so now all the Pull Requests in the queue have to be rewritten and have tons of merge conflicts to resolve. Awesome! 😠

Hey DevRant, this is my first time working collaboratively on a project with Git and I'd like to know what's the best strategy to adopt.

Is it that every member has their own branch on origin that they push to, then we meet and plan out merges when it's time to release? Or does everyone just push to master, but stash or commit their local changes before they pull?

It's a Greenfield project, with just a bare repository on the central server. It's an MVC app where I've decided to do the View & Controller portions and the other person is doing Models and data services layers.

My GF: pull
Me: git pull origin master

😶

Sometimes in our personal projects we write crazy commit messages. I'll post mine because its a weekend and I hope someone has a well deserved start. Feel free to post yours, regex out your username, time and hash and paste chronologically. ISSA THREAD MY DUDES AND DUDETTES
--
Initialization of NDM in Kotlin
Small changes, wiping drive
Small changes, wiping drive
Lottie, Backdrop contrast and logging in implementation
Added Lotties, added Link variable to Database Manifest
Fixed menu engine, added Smart adapter, indexing, Extra menus on home and Calendar
b4 work
Added branch and few changes
really before work
Merge remote-tracking branch 'origin/master'
really before work 4 sho
Refined Search response
Added Swipe to menus and nested tabs
Added custom tab library
tabs and shh
MORE TIME WASTED ON just 3 files
api and rx
New models new handlers, new static leaky objects xd, a few icons
minor changes
minor changesqwqaweqweweqwe
db db dbbb
Added Reading display and delete function
tryin to add web socket...fail
tryin to add web socket...success
New robust content handler, linked to a web socket. :) happy data-ring lol
A lot of changes, no time to explain
minor fixes ehehhe
Added args and content builder to content id
Converted some fragments into NDMListFragments
dsa
MAjor BiG ChANgEs added Listable interface added refresh and online cache added many stuff
MAjor mAjOr BiG ChANgEs added multiClick block added in-fragment Menu (and handling) added in-fragment list irem click handling
Unformatted some code, added midi handler, new menus, added manifest
Update and Insert (upsert) extension to Listable ArrayList
Test for hymnbook offline changing
Changed menuId from int to key string :) added refresh ...global... :(
Added Scale Gesture Listener
Changed Font and size of titlebar, text selection arg. NEW NEW Readings layout.
minor fix on duplicate readings
added isUserDatabase attribute to hymn database file added markwon to stanza views
Home changes :)
Modular hymn Editing
Home changes :) part 2
Home changes :) part 3
Unified Stanza view
Perfected stanza sharing
Added Summernote!!
minor changes
Another change but from source tree :)))
Added Span Saving
Added Working Quick Access
Added a caption system, well text captions only
Added Stanza view modes...quite stable though
From work changes
JUST a [ush
Touch horizontal needs fix
Return api heruko
Added bible index
Added new settings file
Added settings and new icons
Minor changes to settings
Restored ping
Toggles and Pickers in settings
Added Section Title
Added Publishing Access Panel
Added Some new color changes on restart. When am I going to be tired of adding files :)
Before the confession
Theme Adaptation to views
Before Realm DB
Theme Activity :)
Changes to theme Activity
Changes to theme Activity part 2 mini
Some laptop changes, so you wont know what changed :)
Images...
Rush ourd
Added palette from images
Added lastModified filter
Problem with cache response
works work
Some Improvements, changed calendar recycle view
Tonic Sol-fa Screen Added
Merge Pull
Yes colors
Before leasing out to testers
Working but unformated table
Added Seperators but we have a glithchchchc
Tonic sol-fa nice, dots left, and some extras :)))
Just a nice commit on a good friday.
Just a quickie
I dont know what im committing...

git suicide:

git() { if [[ $@ == 'suicide' ]]; then git reset --hard origin/master; git push origin master --force; fi }

gut push origin master

New to working with git in a large scale application. I've used it in personal things, but not at an enterprise scale.

"genius" me: git pull origin {{dev branch name}}
"genius" me: why won't any of these tests work?
"genius" me: spends 2 hours working on fixing some tests

actual genius that I work with: Dude, revert that shit and pull from master, the tests will work. Don't pull from {{dev branch name}} because you have no idead what might be there.

This makes sense. Things are started and abandoned in favor of new priorities all the time. At least my PM is pretty cool and didn't freak out that I wasted that couple of hours like at a previous position.

Also, git is far superior to mstfs. Very smooth and easy to use once you get the hang of it.

What the hell kind of tool is Gitlab? I just want to automatically backmerge hotfixes from master to development. Even fucking Bitbucket had a checkbox to enable this. But not Gitlab, no, you better create a pipeline job in your already unreadable, overcrowded pipeline yml, but oh, the checked out repo in the pipeline is a detached head and you cant push with the user that checks out there. So what, just use a project acess token which revokes after a year breaking your task and then switch origin amd branch manually. But your token-user can't push to protected branches, so create a merge request instead, which requires approvals, making the automated step no longer automated.
But dont worry, you can just use the gitlab api to overwrite the approval rules for this MR so it requires 0 approvals. But to do so you must allow everyone to be able to overwrite approval rules therefor compromising security.
And so you made a feature that should effectively be a checkbox a 40+ line CI job which compromises your repo security.

which nuthead of an architect is responsible for the way gitlab (and its CI) is designed?

iTerm2 & Bash-It. iTerm coz of the split panes, paste history, undo kill session etc so much helpful!! And bash-it gives me so many things, completions, aliases which makes the work a breeze, gpom does a "git push origin master" and many more like these :)

Force pushing a better version in a different language to the repo of a program that I wrote 2 years ago. It was sort of a memory, but I mainly looked at it to feel better about my current coding style.

I don't want to take comfort in knowing that I'm getting better. I know that, and it feels like false affirmation. If anything, I want to know that I'm good compared to others, not compared to a previous, dumber version of me. I'll never get to beat him anyway.

Start managing my bank accounts like they are git repos:
* account checkout -b venture/Some_Startup
* account add .
* account commit -m "Profits and Investments"
* account merge origin master

I should really come up with a better deployment method than `git pull origin master`

Is there anyway to trigger automatically a git clone on ubuntu after a git push origin master ?

So here's a question.
IF i have a developmentbranch that i'm working on an notice a merge conflict in my pull-request. I do a rebase on to origin/master. Then... I have to make pullforward or force push. Which one is more natural to do?