Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
A new way of making bad commits:
alias fuckit='git commit -m "$(curl -s whatthecommit.com/index.txt)"'
Its like Russian roulette with commit messages!24 -
On Friday I deployed to a life site without going through code review or any testing whatsoever. I am now known around the office as 'Billy the Kid'.
6 -
Me: I'm gonna write some code today. Try to push more commits in a single day than I did last week.
Github: You only get half a contribution tile today, bitch.
5 -
SO GUESS WHAT
IF YOUR SHITTY WIFI CRAPS OUT DURING A VISUAL STUDIO UPDATE, VISUAL STUDIO FUCKING COMMITS SUICIDE
MICROSOFT CAN SUCK A BIG, VEINY COCK. IM SO DONE WITH THEIR SENSITIVE, CONVOLUTED, SLOW IDE.19 -
Senior Dev at work told me to cherry pick commits from another branch....later found out that it is an actual git command ! 😅
git cherry-pick <commmit>9 -
Had an interview this morning..
Interviewer - have you used github?
Me - yes
Intw - so, you have a profile on github?
Me - yes (** in mind, I don't think github will allow me without that **)
Intw - how many commits have you done?
Me - ** what kinda qust is this ** well,... Yeah... Umm.. A lot! 🙄
Intw - how much is a lot for you?
Me - umm... Well... A lot lot... So many... I mean a lot of... **Long pause** .... You see, I'm a commitment type of guy. ** Wtf did i just say?**
Intw - Whattt!! Then he laughed.
... and I used to think that my days of embarrassing interviews are over. I'm not going to that company doesn't matter what happens. Shitt 😐10 -
devRant UWP client
3 years, 65 updates, 1.507 commits.
3 users donated a total of €16.97 (~€10.91 after Microsoft's fee), not enough for a payout, so I would say €0.
But it was still worth it, awesome community.9 -
Got together with my old dev team (5) who all left the same company at the same time almost two years ago. (Thats a whole other story).
One of them told us he left and went to a new company that measured performance by the amount of commits a dev would to per day. Of course he didn't know that when he signed on.
Three months into the job he had a week where his first commit wasn't until a wednesday and he got called in by the manager to explain his lack of commits and how he was going to improve.
He quit on the spot. Had a new job in less than a week.
Other devs at the company were fixing typo's and just commiting them one at a time to create a lot of commits.10 -
A coworker blamed me that our git server is rejecting his changes. Turns out his commits are 200MB large each, including binaries of all newly added libraries. And I was all like:
8 -
Someone in Berlin is really into Github's contributions visualization... It even uses it as bathroom decoration 😂
4 -
Changed width:600px to width:500px
git commit - m "optimized responsivity for enhanced mobile experience"3 -
They say developers don't have social lives...
Over one half of my total commits on GitHub have been from just Fridays and Saturdays...
I mean, I guess they're not wrong.4 -
When you push to Github Tuesday/Wednesday/Thursday only, work a Sunday but then take that day off a few weeks later
2 -
Starting a new project
Me: This time we'll follow all the best practices, do atomic commits and write meaningful commit messages.
Coworker: Yeah! Let's start.
40 commits later.
Me: Why is .idea folder in the repository?
Coworker: Sorry My Bad.
Me: 👿👿👿👿6 -
Yo, his palms are sweaty
knees weak, conscience heavy
There's commits on master already:
Your mom's spaghetti code19 -
I have a confession to make....
I just started to use git two days ago.
But atleast I GPG sign my commits11 -
Co-worker: "We would appreciate it if your future commits weren't so ignorant and bigoted"
Me: "Excuse me?"
Co-worker: "You made the gender variable a boolean"
I... But... Okay...13 -
Woke up today to 4 commits from a peer that completely erased most of the work done in the last 2 weeks. After letting my coworker know that their commits were the issue, she insisted that they were not theirs, however they showed her signature.
Love how Git absolutely destroys liers.17 -
Woooooooo!
Just finished my first fully automated CI/CD system. Now all my commits go through the pipeline and gets deployed to live automatically.
It's a small project but still, it's really cool!10 -
Just got a merge request to review. It's TERRIBLE
- 93 changes
- 23 commits
- includes multiple features
- includes new project configs
- includes refactoring
NO. Please don't do that.
Do smaller commits. One feature per MR. It will help you and the reviewer :D6 -
Always make smaller commits! Easy to roll back, easy to cherry-pick, easy to debug when identifying when something went wrong.2
-
The "new guy" just merged master into a release branch.
The build server started bumping versions on the release branch and build "corrupted" installers.
Another developer had to spend a whole day trying to remove all the invalid commits.14 -
*PM looks at my code
*Deletes my constants, replaces with inline strings
*Changes order of conditions (that I tested)
*Hits save --> autoformats code into shitty looks
*Commits: "fix"9 -
I tell a colleague, "Hey, could you make your commits more meaningful? A commit message of '.' helps nobody.".
He then uses 'no message' for his commits.
Also, commits every 30 seconds. I know commit often... But is that really necessary?
Why.7 -
!rant.
Here's some useful git tricks. Use with care and remember to be careful to only rewrite history when noones looking.
- git rebase: powerful history rewriting. Combine commits, delete commits, reorder commits, etc.
- git reflog: unfuck yourself. Move back to where you were even if where you were was destroyed by rebasing or deleting. Git never deletes commits that you've seen within at least the last 50 HEAD changes, and not at all until a GC happens, so you can save yourself quite often.
- git cherry-pick: steal a commit into another branch. Useful for pulling things out of larger changesets.
- git worktree: checkout a different branch into a different folder using the same git repository.
- git fetch: get latest commits and origin HEADs without impacting local braches.
- git push --force-with-lease: force push without overwriting other's changes5 -
$ git push
> current branch is behind
$ git push -f
... 5mins later coworker is asking why his commits have disappeared.6 -
One of these commits due to german network structures.
Everybody wants apps. And expects them to run it in smallest villages
4 -
Anyone wondering whether to go to university or not, here's my commits from summer and when uni started...
7 -
```
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.10 -
I feel bad when I commit too often, especially for little stuff. I'm afraid people will think I just do it to get a higher number of commits :/11
-
today I pull a project to take over from my colleague
today I notice all commits where on master branch
today I leave this world T_T19 -
Fuuuccckkkk! I just realised I made 120 commits over the past 100 hours.
It's a big thing for me as a developer and open source enthusiast because I finally understood how to work on open source projects with a team and also I've been able to give equal time to all my current projects.
Also, GitHub going green is a beautiful feeling xD
So proud of myself lol
1 -
When I wrote a script to automate my commits to SVN... And then used that script to commit itself.... Pure bliss :)4
-
these are the kinds of commits i have to deal with :|
like "it's already past 5 o'clock! i have to leave!"
7 -
The senior programmer at work commits so rarely that in 3 months I committed more than him in 3 years (e.g. 0 times in September)...
What’s the point of having a repo on bitbucket if most of the time the latest code version is only on his machine?
And why I have to recreate and repopulate the db every fucking time because he made so many changes to the structure, which of course conflicts with mine?5 -
Some guy in my programming class just made a bunch of commits with only empty lines and a picture of Kim Jong-un...
3 -
PM: This feature should take you about 6 hours to complete.
Me: Psh if that, it's just a view.
PM: Actually it needs this logic as well. *sends requirements*
Me: OK that's way more than a view... *gets it done and commits*
QA: I need this logic to work a way that was never on the requirements.
Me: Yeah, that's an additional feature but I'll do it. *commits and passes QA*
PM: So why didn't you finish everything on this sprint... you said that 6 hours was more than enough time.1 -
!rant
That momento a friend show me a website that basically lists "last night" commits on projects on github. From what I've seen basically the list commits with words like shit, fuck and hell xD
Here's the link:
http://commitlogsfromlastnight.com/...6 -
I find it really hard to make small, specific commits. I always stumble on unrelated things I want to change.2
-
Emergency change request on a Friday, guy who completes change leaves early, 29 minutes later alerts start going off. Fml.3
-
I'm the best.
I started a project and 12 hours of work and 16 commits later I decide to reorganize the entire project focusing on security and user experience.
I'm a genius.2 -
Am I the only one who doesn't judge a programmers contributions by commits or change history?
Frequently I'm always near the bottom of contributors, because I don't make a million commits when it's broken. And I don't commit lines that will likely disappear in later commits. I like to finish a function, test it, check it, rework, and then make a "made function()" commit, as apposed to:
"Wrote function()"
"Wrote unit tests for function()"
"Fixed error"
"Code cleanup"
"Style guide compliance"
"Reworked function()"
etc.
Sorry that I keep my commit history clean and ensure it builds.7 -
!rant
TL;DR: "Gather all resources before working on any project and committing to the client... & over smartness can be deadly"
Couldn't stop my laughter after reading this one.
A new vacuum salesman knocked at the door….
A lady opened it. Before she could speak... The salesman rushed into the living room and emptied a bag of cow dung on the carpet.
Salesman: - Madam, if I couldn't clean this up in the next 3 mins with my new powerful vacuum cleaner, I will EAT all this!!
Lady: Do you need Chili Sauce with that?
Salesman: - Why Madam?
Lady: - Because there's no electricity in the house...!!!
😂😂😂 -
It feels like you are talking to yourself while commits when you create a github repo and you are the only contributor. :p2
-
We hired a new senior dev. The lead architect is going over basic bit branching and commits with him. This new job already feels like a dumpster covered in petrol.3
-
Expectation: I'm going to spend today debugging my app
Reality: adds 10 new features, 30 got commits and some Easter eggs. No bugs fixed. -
That moment you receive an email: your CI build is failing.
Ok. What went wrong?
Three new commits that do not seem to alter anything related to the failure.
*reverts commits and tries again*
Still failing.
WTF?!
*restarts previous builds*
They now fail too.
FUCK! BASTARD! Are you kidding me?
*investigates*
Turns out that repo of dependency changed and is not compatible anymore.
Argh! Son of bitch! -
Not separating different changes into different commits, and just adding "a few tweaks" when I can't be bothered to list changes.
git commit -m "Added x, updated y, renamed z, and a few other tweaks" -
After going through the painstaking process of getting automation scripts reviewed by the whole team, edits, commits, reverts and finally loosing sanity
and you see the team is still using the old automation scripts in testing.
(╯°□°)╯︵ ┻━┻4 -
So, I forked this dude's terrible project. I faked commits like implementing some incompatible feature. He talks about it on the internet, as expected.
Should I tell him?
Or should I enjoy the show?2 -
Clients be like, why the fuck should I bother to check last commits related to tickets when I can just bother the developer when he's about to sleep...
7 -
When you change 200 lines of code all over the place in a class and then realize that you forgot to pull 17 commits from origin 😖2
-
As a programmer doing sports, the only thing I think is: Shit, when my MacBook falls down, I will lose 13 unpushed commits.
10 -
So we were supposed to have another good build today.
Supposed to.
This one guy on our team gets weird sometimes, and refuses to commit his shit until the last minute. He says "Don't worry, I'll handle all the merging, it'll be fine!"
What he forgets is that much of our code relies on his! His latest commits reworked a couple entry points and a class definition. No backwards compatibility.
He made his commit, and nearly our whole stack shit the bed. Jesus jumping Christ. Weekend? Nope.2 -
> "you've been slacking off in development go do some damn work"
> 20 commits since yesterday
> guy isn't even the project owner1 -
There should be a "Did you get latest? There have been 'x' commits since you last opened this project" dialog box when opening any team project.3
-
Why squash commits when you can just --amend the commit and git push -f
#SecretsOfADumpsterFireDeveloper4 -
Little story, about how i get things fucked up.
I've been working for two nights on some project, and we have notifications in slack about new commits, and i've been working for myself, not pulling any commits for this time, cause no notifications 've been received, and then when i've tried to commit&push i've realized that there is 14 commits before me, and someone just accidentally turned off notifications :C
1 -
I take a colleague's project... and find this. How? Why? It was a small feature and now I have to maintain it. Fuck!
3 -
Just wanted to fix one little thing. Ended up with 20 commits for 35 other little things, three branches and realizing at the end of the day that the one little thing is still not fixed. Story of my life.3
-
No commits?!? Well, maybe you should fucking make up your mind about what the fuck you actually want! I don't give a flying fuck about your pathetic excuses. If you don't get me a final spec, then don't try to skin my back about not delivering updates and "not showing active progress"!!! FFS!2
-
When you debug a project on someone else's computer, and then commit push, and the manager tells you that you dont have enough commits . Fuck it.2
-
It sucks having to revert 2 days worth of commits all for some issue that I can't independently confirm actually exists. Site owner has panicked and wants to hit Ctrl-Z back 7 commits. There goes two days of my life I'll never get back.3
-
Just found this awesome function in the old commits.
def clean_cache():
'''
This function cleans the stored cache in every update. Make sure to call it before every feature addition.
'''
print 'Cache is cleared. '
return2 -
Got a nice PR merged. Happy because it's on a popular project with over 4k stars. Ashamed because 50% of the commits are changing indentation from 4 spaces to tabs 😌1
-
PSA: If you need to make dummy commits to trigger a pipeline for test purposes, please just use --allow-empty and make an empty one. Don't just add random newlines back and forth in stupid places.6
-
was invited to contribute to a project. after about 60 commits in a row, multiple refactorings and several added modules it feels like having highjacked the project. the owner sits in silence. prolific but awkward.2
-
Is it that difficult to write a fucking commit message? I've told this guy 3 times and he still just commits 'dev' as a message.4
-
So why the fuck did you go into code that I've written, change the name from "mode" to "type" throughout the >1500 lines of code that's relevant to the feature, and then move on to change my implementation to something that is arguably not common practice for the language and framework we're using, and in turn create duplicate state? And why the fuck weren't these changes in separate clear commits, but instead scattered over multiple commits? You're supposed to be senior!3
-
An hour of "WHY ISN'T ANYTHING WORKING" followed by ashamedly squashing 20+ local commits and actually remembering to git push the result that time.1
-
Well since vim & git has already been said gpg. you can use it as ssh keys and sign your commits to make sure nothing nasty is added to a git repo under your name
-
Achievement of the day:
Reverted a merge from 3 weeks ago (about 30-40 commits back), 1000 ish LOC. Didnt break the build, app worked 100%.
Can't shake the feeling my desk will literally be on fire tomorrow tho. -
Being able to properly name branches/commits in git and holding back from the tempting "I'll fix that along the way too" is an art on its own
-
does anyone else purposely make separate commits and push to make their commit history darker shades of green? I think as new developer I have a disorder and bad habit.6
-
My plan/resolutions for 2018?
Have at least 1 commit per day w/ maybe exceptions like special holidays and such 😁
(No commits just to have a commit like adding a line of commentary or stuff like that)
#iwannabetheguyshetellsyounottoworryabout -
As I went through old open PRs, to sort them out and resolve them, I started to feel you do when you look at your childhood photos or in case of YouTubers at their old videos.
That is to say, I'm dying of shame.
*Well at least I'm cleaning them up now so~*3 -
*working at a project, currently creating commits and pushing to remote
I created an early PR with a title [UNFINISHED] and [NOT YET DONE]. I'm really not finished yet. lots of stuff still need to be committed and pushed to repo
And suddenly, I find out that my team mate - just out of the blue without any prior warning - MERGES THE PULL REQUEST
"oh hey there are conflicts in the pr you made"
YEAH WELL MAYBE TRY GETTING YOUR HEAD OUT OF YOUR ASS WHAT IS WRONG WITH YOU ARE YOU EVEN SANE
So now what happened is half of my commits are merged, he didn't tell me, i pushed more commits, branch recreated, and then he reverts the merge. so now everything is really messed up :)AS)D(F)AEF)SDF)AW)sfdjsigkl;zfghlkkj ghaslkj;gabsd;lkgjabslkfgh GET YOUR HEAD OUT OF YOUR ASS I WANT A PROMOTION3 -
*Commits the work with a typo in your commit message*. Shit. Commits again just to change the message.
#alwayshappens1 -
Oh my effing goodness...just went through the repo of an app we're working on and this new dev in our team saved his commits with, "ok", "done", "fixed", "another one", "arrggghhh!", "wow!"..."not complete"...for fucks sakes...DUDE!1
-
Boss fast tracked a release for a customer. No testing. Not checking commits or the state. Undocumented requirement brings down everything and everyone is running around with their hair on fire. Sigh.2
-
Intern - adds commit message like "added two files"
Me - Hey Intern, I've added commit lint, please don't disable precommit hooks.. so let's follow standard commit message format
Intern - commits like "feat(app): fix changes"
*later*
Me - Hey Intern, please commit with short meaningful messages like what actual changes were made
Intern - commits like feat(app): whole long story of what he couldn't do and some changes..
Me - 🤦5 -
I finally (sort of) understand how to perform an interactive rebase thanks to a single enlightening article. Not sure why nobody explained it so clearly before.
This will make my half-baked commits much less embarrassing.5 -
Tfw when you're lying down falling asleep and realize you didn't commit your work but you turned off your computer.3
-
This is about both worst boss and most annoying co-worker.
Well, this boss didn't care how much code we wrote, or how good it was (well, at least he didn't care that much); only how much commits we do. And this coworker literally did a script to do a commit every 10 minutes. 24/7. Everyone else was completely mad about it and about a week later we achieved that he was kicked from the job. Since then I still get trauma if someone commits something unimportant.9 -
Android fan boys: WOW! Android O Dev Preview released! Time for numerous commits.
Apple fan boys: Apple so needs to implement these features in the next update 😂 -
GitHub appears to be operating in some sort of time paradox at the moment as none of my recent commits are showing up.7
-
When you mess up the repo, the bestfriend to help out is named "stash".
Personal record: 9 times stash in a row with no commits.
Comment to share your personal records...
4 -
!rant Still feeling poorly, so still making commits on "fever" branches, but that doesn't stop me from making a new thing and deploying it from a fever branch! *maniacal laughter*
https://cat-icons-for-great-good.netlify.com/...8 -
Yet another rant on cooperate world
The other day my colleague was telling me that he was with very senior architect (so called architect, who keeps on changing things on the fly) and when my colleague was telling that he doesn't have resources to work with, this senior architect opened up stash (Atlassian Git) and opened up profiles with names and was looking at commits in the git...and said "this guy doesn't have commits for long time...he is free"
WTF.... 0 0 -
A) "Why did you do that?"
B)<typing>
A) "Hello? I'm talking to you..."
B) "Sorry, i missed to tag this Commit. please see the commit history for your questions. That's why i use the DVCS.1 -
I append text from http://whatthecommit.com/index.txt to my commits automatically every time. So today I made the most useless commit and they added the most appropriate message in the brackets:
Updated datastructure of sorts (should work I guess...) -
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.1 -
principle software developer who does not code, design, or architect,
instead, do random eslint fixes which create conflict with everyone's branches.
1 line of code "fix" per commit.
there goes 26 commits1 -
That feeling when you're almost done with your personal project using an entirely new language and framework :)) been working on it for the last 2 weeks. 62 commits in!!2
-
I am an amazing programmer, but without the required skills
My git commit history is pristine, but without the commits4 -
Senior dev:- "Limit your commits to have maximum 10 changes"..
Also senior dev:- Doesn't approves pending merge requests for days...5 -
Guys at work just found out that they can see all the commits in a repo that they have to change stuff in on a daily basis..
Granted they aren't really the most tech savvy sometimes but they have both been there for like a year...
Made me laugh a bit when one went
"Dude did you know we can search our git for commits? So we can look for who fucked up!?" -
My biggest bad habit (for now!) is rushing changes. I have no real deadlines, yet I rush commits and cause failures in our CI tool every week1
-
Honest question:
I did a project and delivered it, but my boss did 4 commits after that. Without giving me any feedback.
They were small things: using a different library (just one line), and removing one debug line that caused a bug.
Should I ask him for feedback or just tell him "Hey I saw your commits, I'll make sure to use the new library and never let any debug line in"?7 -
When the project manager commits a build that's broken and then blames it on you...smh
Learn to compile a successful build before you commit the change out to everyone!! 😤 -
Today I woke up 🌅 wanting to write code that is more art 🎨🖌️ than just the usual dry technical stuff...
I want to look at my commits this afternoon and feel proud about mastery and craft!2 -
Those people who don’t even understand the commit message
Who commits using commit message “commiting”?3 -
I have a unreasonably large amount of commits just for these files in the repository.
Is there something wrong with me?
5 -
Me: I should divide my project in small parts. It will be a piece of cake.
Also me: (on last day of submission) 76 commits in 34 minutes.
*Face Palm* 🤦♂️1 -
Welcome to Git, where when you try to split a commit you end up making 8 more commits than you want.
Based on a true story, today at work -
git commit -m "Now we have a not a true scatter scatter chart"
I mean, what's the worst that can happen, my commits are very informative. -
Readme.md
*Todo: Add description*
>103 commits
>Last commit: a year ago
>Last commit on readme: 5 years ago
Slothful cunt, you don't deserve these 7 stars -
Team leader doesn’t know the difference between merge/rebase nor uses pull requests to propose changes to a humongous repo, just two branches where everyone commits and pushes freely! 💩💩💩1
-
When you think you know something and you can close the Task in a day ....
But your manager adds requirements at every stage and it's been 4 days, 50 commits but the task is still open ....
Manager Y U Do this? -
Got branches:
+ More organised
+ Easier to work on lots of features
+ Easier to collaborate
- Commits don’t show in github contributions
Result: no branches1 -
Writes a slot of code,
Closes laptop and goes for sleep,,
Wakes up opens laptop
commits and git push
and sleeps happily.
who knows there might be robbery at night, or fire in home or may be earthquake. -
So I hooked gitlab pushes to show on slack channel... My coworkers don't have a clue about merge, commits, anything.... Sometimes looks like they have no clue about most of the things...
-
In every team there would be a "git spammer", who always commits on top of other's commit just to increase the number of commits.
😕🤬🤯3 -
Git cherry-pick 35 commits, another dev commit to the wrong branch, and these commits will be released first
-
The hardest part in my job these days is thinking commit and PR messages :/
I believe my code and commits and PRs are always self explanatory, the company doesn't agree apparently.2 -
My teammate doesn't understand that the quantity of lines/method that he does in one commit nor the number of commits he does in one day translate directly into the quality of his commits.2
-
Absolutely hate it when my software engineering module project mate merge their own commits into the team repo without anyone else reviewing.
That’s it for you, branch protection ON. One more time and you’re losing push access -
It's a nice feeling. Even if the commits are rather small.
Edit: Should say "you've pushed" rather than "you've commited".
2 -
Today, a colleague requested a merge with 5 commits, but only 3 changes. He must be a wizard or an idiot.1
-
Those 'HR tools'. 'Workforce Management'.
Once the company commits to it, they stay in use long after their interfaces have become clunky, their features outdated. Pretty bad UX.
Expense reports. Time Sheets. Leave Applications.
I'm looking at you, Kronos. >.< -
Me start reporting at Standup about my recent work. My Teamleader start talking the same time, saying he has seen the commits and I don't have to go into details anymore.
Thank you asshole for disrespecting me and my work.3 -
Today's story.
1. Git commit all changes
2. Need to git pull bcz of master change
3. Mistakly did git commits undo.
All my changes fucked up.
At last
Ctr+z saved my ass -
I Love git. After a year, I still can't decide how to break my commits up. Should I create a new commit with every level me of code, or every function or feature meaning (a few functions). What are your ideas?33
-
Dem feels when you cba setting up a project locally but want to use Git anyway for when you can be arsed... new repo once it's in a better place!
3 -
I added this message to one of my commits:
Untested as Windows is being difficult and won't let PyQt run and Linux us being difficult and won't boot, but probably works
😉3 -
Great. So my laptop just died and it's time to send it to RMA. That's not a big deal. except I forgot to push few commits and now there's no way of doing it. Just great3
-
Why do some people on github just randomly fork projects without chaning something and their github profile is full with forks which never got changed and be like "this fork is 173719293 commits behind"3
-
I never understood why there are screenshots of commits being like test, test2, does it work now? or WORK YOU SHIT..
..until i tried to gitignore stuff a bit more specific while gitkeeping folders and deploying shit relying on CORS.😂2 -
Remember that git commits are just like commitments in a relationship.
Make them small and avoid the big ones.4 -
Why eclipse?
Why did you think that implementing git yourself was a good idea?
Why? Fucking why?
Now when I switch to my development branch and it's a few commits behind I get lock fails when I fetch. And when I pull?
I'm fucking 32 commits in front of the branch? Like what the Fuck eclipse?
How can you pull those commits from the repo without fetching?
... I use the command like now.3 -
Going through my git commits and wondering why I would just commit every file under the same commit. More often than not they had nothing to do with eachother 😐2
-
I'd argue to say that committing often, even if the commits aren't always meaningful, has saved me numerous times from bad code gone awry.
-
Facepalm of the day:
My coworkers commits third party libraries AND the source code of them. Of course, the source code is never used.1 -
am i the only one who likes quoting Blazing Saddles in git commits?
most recent being adding mongo to a project.
-
I'm learning git and i must confess that i've been thinking about use sourcetree gui to make my commits, may be i'll try it tomorrow6
-
Question about GPG:
So I understood the concept and successfully applied it to my Gitlab, but how helpful is it?
From what I understood it helps detecting which commits are from verified authors and which are from just someone who has access?
I'd appreciate if someone explains more on how helpful it is :)
5 -
HR declared day as holiday.
You Resume work next day and Git commits channel had 400 unread messages,
Silently telling at you like - hmm lazy lots get back to work!
To the hard workers You could’ve waited to push your commits the next day brother, we know you don’t like holidays like we do. -
More frequent commits are imperative to your sanity!
Trying to find a code change in git, and I stumbled across a commit comment I can't even remember doing!
1 -
Testing builds remotely with pushes before testing them locally because I'm too lazy to bring up the local CI server.
Ending up with over 9000 "Testing build" commits.1 -
Honestly, I love using the GUI and the terminal in combination when it comes to Git. I feel like I'm faster doing just general commits (hint ctrl+enter commits your work).
But I use the terminal when I start getting into the weeds, like checking out, resetting and doing stuff with my branches.1 -
When your boss makes you suffer from imposter syndrome, just because he commits something which doesn't exists !!! 😣
-
6hrs trying to get a static and dynamic cell working in Swift. Xcode crashes and not a fucking thing was saved! My git commits make no fucking sense!4
-
And I thought I knew a lot about practical git... But today I learned about fixup commits and autosquash. Awesome!
-
Doing some group assignments for uni
Repo 1, 60, 7, 2 commits
Repo 2, 200, 12, 1 commits
Repo 3, 55, 10 commits
You can guess which stats are mine.......
And then on the reports I have to do all the work cause I wrote all the FUCKING code ... FUCK8 -
Is there a way to recover a deleted GPG key on GitHub? My old key expired, I generated a new one and delete the old one. Now, all my old commits are unverified.5
-
Hey guys,
I'm trying to convert a SVN repository to Git and I want to keep the history. So far everything has been going more or less good but when I push the history (of commits etc.) doesn't get commited too. Is there a way to change that? What do I need to do to get my subversion changes/commits in git?16 -
tfw when a library's test are passing but when you implement it, the same library's (dependency) test are failing.
*Raises an issue on GitHub*
MY 4 COMMITS ARE FAILING SINCE LAST 4 HOURS -
Why tf does Bitbucket always fuck up commits after 3am........
190 file changes happened - only one was commited....11 -
The owner of a github repo has added me as a contributor but haven't given me write access, so i can't push commits.
When i asked him, he said i have to make PR. The fork button is also disabled. So i guess i can't make a PR also.
Now WTF i am suppossed to do now?
No write access, fork disabled . Still i have to push my commits ....ughhhh2 -
Those bugs that gets fixed by creating a new branch and doing the exact same changes there or even cherry-picking same commits there. Not the first time this happened to me :(
-
I always commit even if i just add a new line in html.
I can do 10-15 commits a day. Is it bad habbits or good habbits?5 -
Started a new job and seeing the commits and notifications on Github while not understanding what these people are doing yet, makes me both excited and frustrated at the same time.
-
Stayed up till 3am yesterday playing pokemon moon, and still have pushed 2 commits before 9am. WhoNeedsSleepAnyways1
-
I have a git feature branch with my commits but also have merged the changes from the main branch to resolve merge conflicts before PR.
But now need to create a special release with just my changes.
So I think have to cherry pick all my commits on my branch some the last Release. How can I do that?
Develop (others) + Feature => Develop
Want to create new branch
Last Release + Feature (but only my commits since last Release)3 -
Please, Teamcity, fucking learn that different commits relate to different branches!
So hate that piece of shit!2 -
Question about git. I worked on dev branch and made 10 commits.
Then I squash merged 10 commits from develop to master and made a release build.
Now problem is if I make a pull request from develop to master bitbucket will still show that master is behind (because develop has fixes in 10 commits while master has all of them squashed in 1 commit).
Now my question is whats the best way to make sure master and develop are synced (basically that master would have everything what develop has) ?
should I just merge master into develop back after the release?9 -
Fuck. I created a branch from beta instead of our production branch. This is why I always check my commits before pushing...2
-
I'm at the moment..... after a 100 commits in one single pull request, days of torturous effort and grappling with a stupid bloated piece of crap software, when, I realise, I COULD HAVE JUST TOLD THE CLIENT TO BUZZ OFF!!!
-
Were ganno play a game: whoever forgets to remove prints() inside of his commits has to da an allnighter to fix the most difficult issue.
-
Since we are sharing some of our more interesting commits, what do people think of these commits?
General: pro.user update
297af8f
Refactor: Hide and show Spin Boxes on Normalization
6a4e1f3
Refactor: Dynamic resizing refactoring
964f0ae
Refactor: Dynamic resizing across any screen
5890a35
GUI: Measure screen size and assume the proper size.
13f2cb4
Fix: guitest.cpp has been reafactored
5cbc1b4
Dir: Clean unused directory
32c8384
GUI: Hide and show Spin Boxes on Normalization
84db444
Commits on Jun 28, 2016
GUI: Make boxes more bolded
3d23952
General Commit: 11:03 PM 6/28/2016
678c249
Del: build from previous commit
e428041
Fix: Guitest's compiled code was broken
25f546f
GUI: Make window scrollable.
07091fd
Adjust; Changing directory tree -
!rant
To embrace the TIFO (today I found out)
$git rebase -i <hash>^
You can reorder commits and squash.
I just used it, to amend a commit that was not HEAD with some changes I’ve done later.12 -
Git Semantic commits. Any thoughts? I just came across this today. Any tools you could suggest? I came across a command line tool for feat, chore, test, bug, fix etc. by russiann on github should I run with that or something else?
-
I played around with Git Rebase today to learn a bit about it, and it was fun, but in the process I completely obscured my process and erased a commit that has a published artifact associated with it. What remains is a few incremental preparation commits hoisted up from today's cleanup, then a pair of commits on two projects both of which only compile against the version of the other repo built from the other commit.6
-
The feeling when you get to offload a few days worth of commits after a change spiralled out of control
-
This was my first week as Jr Dev. I'm excited, first commits, PR, issues and hotfixes. Any advice for me?
Have a nice weekend!! -
What a great feeling it is to fix my remote in origin and finally push my first commits as a programming newb! Thanks Google!
-
Does anyone else contemplate timing their Github commits for the next year or so so that there will be a shaded picture when someone looks at their profile?
-
I wonder if an AI is trained with a set of requirements and a corresponding set of commits, would it be able to add by itself some simple functionality?4
-
When somebody doesn't squash their commits. And I have to look at commit with that line they deleted. So annoying!
-
Sumbitting a succesful Pull Request with a couple of commits to a public repo just using GitHub desktop is like playing life in Legend mode1
-
TFW your collegues rename and refactor everything, don't comment on their commits and then break EVERYTHING when you merge their changes into your branch. FFS.
Top Tags
Weekly Rant
View