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
-
I just did git branch in someone's repo and got this ..
master
master_backup
master_bckp
master1
master_aug17
I'm armed and ready .. !!
😐😑😐😱😩😡14 -
Please do rename the "master" branch to "Führer". The umlaut will probably catch a bunch of applications that aren't UTF-8 ready.15
-
Welcome everyone.
Today I signed my first contract!!!
Front end
Part time
I'm 30.
This is still a start14 -
Pro tip: NEVER work when you’re tired, and if you absolutely HAVE to, make sure you do it in your TIRED branch.10
-
"The password must be 6 to 32 characters long and must contain atleast one uppercase character, one lowercase character, a special character, the md5 hash of your last name, a dried olive branch and the blood of a unicorn."6
-
"I'd rather post my nude pictures in slack than this unfinished feature branch... I would just feel a bit *too* naked"
— coworker4 -
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 -
Confession of the day:
1. I work in release mode
2. I work on the main branch only
3. I test on production13 -
Mastering git has become the best thing ever. I feel like a real code monkey. Swinging from branch to branch. Eating all the bug-eeee eeee ahhhhh oooh aaaaaaAAHHHHHH!2
-
What do you mean the master doesn't build? How can it not build? Stop breaking master! It is not your personal playground branch for 🐙🐙🐙 sake!!!6
-
- Merging 300 files from one branch to another in TFS.
- No merge conflicts.
My first thought:
This can't be right. I must have done something wrong...3 -
Dev deleted a branch I was working on. When I asked him why, he responded "I don't know. I didn't create the branch so I thought I could delete it"
Frack!9 -
Me: Damn it guys, you broke the master branch again.
*Fixes master branch*
*15 minutes later*
Coworker: Bro, master branch is broken again.
Me: Oh for fuck's sake, who did it this time?
Coworker: You did.
Me: I have become the very thing I've swore to destroy.1 -
My computer science teacher won't stop developing on the production server 😭 he switches the branch on the production machine to dev all the time and merges broken code into master. Kill me4
-
So, at my company we are migrating from "master" branch on github.
It's good to know we are defeating racism.57 -
Teamate: Hey I'll checkout you're branch to see what you've got done today.
Me: ...Ok.
Few hours later Teammate forgets to change branch and overwrites all my code in my branch causing merge hell and creating hours of more work.
Me:...what in the f***?!
6 -
3 hours of productive coding in the morning then 8 hours of swearing, cursing, searching stack overflow, reinstalling eclipse and git only to realize in the end I was trying to push into a "protected" branch...
Why? because i'm stupid...5 -
I need sleep. Somehow I managed to create a file named ":w" and a git branch named "_D".
Writing "git branch -D _D" was the weirdest thing ever.6 -
My team mate has just found the best conditional statement I've ever seen, in a source code he received from the client.
if (1 == 1)... and it has an else branch :D11 -
Fvcking project manager wants me to commit my partials code to the master branch just to let our employers know that we did something today! That's why you are there to relay our predicaments to them, you piece of shit!
Now he is insisting it the whole team. Fvck! Are you nuts? Do you really understand what version control really means? Why master branch, why can't we just create fucking different branch and push it there if they want reference! Commits are supposed to be a fix code or update not a broken and unfinished piece of codes! I will fvcking cross my finger after messing up the master branch. Now it looks so disgusting to me.9 -
My first contribution to a GitHub project was finally merged to the master branch today! It was just a bug fix but it’s a start!!11
-
When you accidentally commit and push under the wrong branch and the wrong branch in question is master.
6 -
I wish there is such thing as branch in a relationship. So that whenever a couple are having a fight, they can create a branch and work their shit out in that branch and eventually merge to the master branch.
Wait
Merge....
That just costs.... more conflicts3 -
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 -
$ git push
> current branch is behind
$ git push -f
... 5mins later coworker is asking why his commits have disappeared.6 -
Just saw a repository with branch name - 👶
bitbucket gives this - git fetch && git checkout 👶 for checking it out,
wondering how would anyone checkout this branch without copy pasting the above line from the web xD8 -
Today `master` turned into `main` for me on Github and I was like "wait did someone make a branch on my repo."
Should of been called the "magic" branch because shit breaks for no reason like magic.19 -
Starting a third year computer science course. Lesson 1 of web API production. Git. Lecturer tells us to do a different branch for every commit so it's easy to roll back.
Nice.8 -
```
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.11 -
"Server deployment is automated from git, so dont merge things into the master branch without permission"
Oh ok
>i create new branch
>push unfinished code because i gotta hurry
>server breaks
Well golly gee seems like you did a shit job at automating7 -
Android oreo made me change so much code and broke so much shit like background services that my latest branch in git is FuckAndroidOBranch
6 -
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 -
Please, stop being afraid of git rebase.
Please stop merging master branch into feature branch just to fix pull request conflicts.2 -
Recently someone from QA came to me yelling "Why did you push to master? You have a feature branch for these changes..."
I replied "Indeed. Coincidently it's called 'master' "2 -
dev: Can you add a master branch to the following Git repositories ? They are newly created and we don't see any branch.
me: Whaaattt are you asking ???
This is how the day started.
#quadruplefacepalm1 -
!rant
I'm freaking tired of telling colleagues at work not to create feature branch in upstream and use their fork instead.
Turns out idiots can't recognize the difference between a forked repo and the upstream.3 -
How can people use git like that ?
Paris' metro has a simpler network.
If you can stop yourself from all working on the same branch at least do `pull --rebase`.
4 -
LPT: Name your branch after your user name.
If you select the branch in your IDE the status bar shows "Checking out dbx12". So at least someboddy is checking you out. -
Our marketing just change the blacklist/whitelist terms to blocklist/allowlist to make it more "neutral" following change in github "master branch" to "main branch"
When will this end, people ?
:/14 -
The moment when you made branch restrictions, but your colleagues just remove them so they are able to merge their branch into master.2
-
Today the Git for Windows updater asked if I wanted to let Git decide on the naming of my default branch... Hell no snowflakes!17
-
When some one at the company decides to branch off from the main codebase and end up with several outdated and separetely modified branches for two years.
Yeah nice work genius and good luck with resolving over 250 files of merge conflicts.
Just kill me now 😭1 -
[First rant] When you commit the wrong code to the deployment branch.
This happened to me yesterday 😅 Reverted it but everyone knows what I did by seeing the commit history
5 -
Most of the work we do is committed into various branches. Everything is merged into the master branch.
Colleague was on vacation. I was working on a bug that was fixed by him some time ago. All I had to do was find the commit and merge it into the relevant branch. I didn't know which branch to search so I just looked into master. Search all commits on master made by colleague.
All I see is:
"Merged into master"
"Merged into master"
...
"Merged into master"
MERGED FUCKING WHAT INTO MASTER?4 -
Current work project: Ok where is the master branch?
Coworker: Oh we lost that one a few months ago due to some merge conflicts...7 -
Source tree opened
Finds new option 'cherry pick'
Wtf is this
Clicks on it
Wooow, there goes my master branch again4 -
I made some changes in existing repo on my own branch. Created PR for it to be reviewed and merged into master.....
That was more than a week back. But senior engineer never merged it.
Today I see that he closed my PR, deleted my branch. He created his own new branch, added my changes and some of his changes and created PR.
What shit is this?5 -
Quick maffs:
git checkout -
will switch to a branch you previously checked out. So you can quickly switch between branches8 -
Thank you, GIT. Thank you. Your reflog saved work of months after someone deleted the wrong branch.1
-
Minimal comments, no tests, push to Master branch... *Cough* though, this is all for personal projects, not team projects.2
-
Github is again down, I wonder if they triggered deploy from wrong branch.
Fuck this shit, moving to selfhosted solutions:
https://gitea.io/en-us/13 -
Annoying git cli inconsistencies:
git branch --list
git stash list
Lost count of the times I have entered
git branch list7 -
Aaaa stop this issue with renaming everything furcubimofawasggkdjgdkkf whitelist blacklist git blame and the master of em all, the main branch3
-
New dev at our company. After two weeks he has finished a feature for a project. Want to merge it into the dev branch ... he worked in the master branch.2
-
Terminal Devrant has been updated and now works! , Images are up an.
All is on the alpha branch.
https://github.com/Supernerd11/...3 -
OPEN SOURCE CONTRIBUTION
Original post link:
https://linkedin.com/feed/update/...
Start your open source journey.
To Push your personal project to GITHUB.
1. git init
2. git remote add origin [link]
3. git add .
4. git commit -m "commit message"
5. git push origin master
To contribute to someone else project use the following steps:
1. Fork the repo.
2. Clone the project in your local directory using git clone [link]
3. After clone, create a new branch. git branch [branch name]
4. Checkout to new branch created using: git checkout [new branch name]
5. Make changes in Project then 'git add' and 'commit'
6. Push back the changes using git push origin [newbranch name]
7. Open Github web view and click the pull request button and you are done.
Follow Up Post: https://lnkd.in/fEMbTPC
GitHub Link of GIT-CHEATSHEET: https://lnkd.in/fhy4hmu
HD VIDEO: https://lnkd.in/fmq8GTd5 -
Someone who was lazy to make changes from dev branch, making code only in production without updating dev then wanted me to merge from production to dev because he was scared ☺️
-
See code of a dyslexic intern
Neither do I want to correct him without knowing it to be respectful nor do I want to work with this code
> mfw his branch gets merged into core
4 -
Day 1. Push branch. Make pull request😀
Day 5. Got reply to fix some silly stuff🤡
Day 6. Apply changes. Ask for review again.😊
Day 7. Needed to work for another project for two weeks🤝
Day 25. Came back and pull request and branch were deleted from server 🧐🧐
Day 26. I merge my local branch copy into master and push it to server. So long bitches! 💅💅6 -
When you just merge master into development branch and whole Jenkins wall turns red. Wtf? Wasn't me bro.. o.O
-
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 -
People who willingly install and use development branch web browsers and then send inages of exploded websites when using said browsers.
-
!rant
For people like me, always committing on the wrong branch, this is fucking awesome:
https://github.com/jimeh/...2 -
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.2
-
My new team mates type in the date and time of commit on their commit messages and maintain code only on master branch. Some people deserve have their write access revoked.2
-
When you offer to help out a fellow coworker on the top priority feature he is developing and he just sends you the branch and stops working on it.2
-
Don't rebase and force-push a shared feature branch that's still in active development. FFS. A "senior" developer should know better.1
-
That moment when the code doesn't compile due to an error in a different module that you never touched after merging the master branch into yours...1
-
An amazing git story: A month ago coworkers did research and started with merge requests. Their workflow is as follows: A Feature is developed in a branch, then a merge request is opened. After a very short review it will be closed (rejected) and merged without request. (wtf!) After that the develop branch will be tested later, in case of bugs, a new branch per feature is opened.3
-
"There's a branch on terraform-our-project called instance-rols"
"Can you send me a link?"
OMG are you really so fucking lazy you can't go to the fucking git web interface, look up the damn project and click on the fucking branch?1 -
Biggest sin? Easy. Pushed directly to master branch and deployed to prod. I should mention it was something very small before I get crucified😂
-
I guess I'm doing something right.
The branch executive just asked me why I haven't taken any time off :O5 -
When you git cherry-pick for the first time, screw up, rebase-drop, repeat, screw up again, and end up just pasting the correct versions of the files and commiting on top of the branch.
Dirty, but it works.4 -
Our Other it team asked me to create a new repository instead of a new branch in my project just cuz they thought branching would be more time consuming than maintaining a separate repo for emergency bug fixes.
-
Did the MIT seriously just take down one of their own huge tiny image datasets for machine learning because of the same problem as GitHub's Master branch?12
-
"Could you help on project X and implement that straight forward feature?"
So I clone the repo. Run the tests in the main branch. 20 tests fail.
Yes, this will be fun and very simple ...2 -
!rant
True its a two days old story but now ReactJs 16 is out, and license is now MIT.
this is a good way to start my day :) -
git stash pop'd on wrong branch, hadn't realized it until after a bunch more work. Then continued screwing things up and unit tests are failing.
This is not a good coding day. -
Why fucking my coworker push not compilable code on master branch??
Ok we are developing it, no yet release but I can't compile it for my tests.
4 -
I'm too lazy to set up a proper code review from a branch. Instead, I just make dozens of quickly obsolete tags. I should probably learn to use subversion better, but... ¯\_(ツ)_/¯
-
If you're having merge problems I feel bad for you son, you've got 99 problems but my branch ain't one!1
-
I forgot to create a branch and pushed directly to master...
Thankfully nobody reviews my code in this project or gives a shit anyways2 -
Webpacker works on branch master.
Webpacker doesn't work on the "back-end" branch.
I didn't touch anything javascript related between the branch's creation and now.
Why. Why why why why why.
4 -
TEAM MATE: let me sync my branch with upstream master
*starts typing*
git pull upstream master
ME: Nooooooo!!!!5 -
Commit changes that is working perfectly.
Goes on vacation for 2 days.
Comes back to work and only half of my changes were merged to the test environment.
Also, the merge master decided to update my branch with the test branch.
Nice... now I have to redo most of my work.1 -
CTO pointed out a typo in my branch. Agreenment.
I think I'll have to search for a new workplace 😢4 -
Main branch running locally - fine
Main branch locally connected to QA dB - fine
Main branch on QA server with QA dB - NOPE
OK - build main locally, push to QA server - fine
WTF.jpg
Main build by build server, push to QA - nope
Rebuild QA vm and dB - build main, push to QA - nope
Turn on full server logging - PASS.
MAXIMUM WHAT -
Remember this : https://devrant.com/rants/1547095/... ?
FINALLY some updates.
Just to say they deleted the branch I was trying to merge on during the month, so I need to redo the pull request and rebase.
(ﾉ｀□´)ﾉ⌒┻━┻5 -
Forgetting to switch the git branch from master to back to Dev after committing. If I had a penny!4
-
Shoutout to any CommBank developers, I've been dreading going in to a branch to open an account - turns out it's only a 3 minute exercise using the website 😌👏 👏1
-
One of my colleague uses git prune to make a local branch track origin. I told him the way to do this (git branch -b newbranch, git branch -u origin/whatever). He says why do it in two commands when you can do it in one. I asked him what do you think git prune actually does? He says, "Who cares?". It pains me deeply.
-
Is it just me, or does anyone else find it extremely satisfying completing a successful git push -u origin master?
-
Executing git commands you found online as proposed solution to your problem without checking what they do. Not even once.
-
When I have a Jenkins build fail, then fix the issue, I run the build four more times manually to make that branch "sunny" again.1
-
Today I heard from a fellow worker: "Why this lot of conflict in this branch, the conflict that I have at home is enough".1
-
It's only took me all morning but I got git properly setup on our server.
We have a folder in the repo that holds the distribution files. They get split to the distribution branch. Then the hosting service clones that branch.
Finally we we got some proper version control and a good testing environment.
Oh yeah the distribution files are minified using grunt. -
Got branches:
+ More organised
+ Easier to work on lots of features
+ Easier to collaborate
- Commits don’t show in github contributions
Result: no branches1 -
Client A asks for Feature A. Devs start working on feature A. Client B comes in asking for Feature B. Management tells us to stop everything that we're doing to work on Feature B. Client C comes in...
We end up having tons of branches with half-finished features, and the product never improves1 -
Merging one git branch into another when it conflicts an added line or function.
Like really? You can't handle ONE LINE being added?6 -
15 mins before the Production Release, after accidentally merging the Dev branch with the Master one :)2
-
There was this guy at university who pronounced 'branch' like 'brunch'. It was so hilarious that my friends and I had to hold our laughter back.1
-
When you use Git for the first time and your project from 29 commit jump to 62 for continous error with Pull Request.
Of this new 33 commit, only 3 are REAL commit.
Four hour for reset and fix all The master branch.
But finally all is fixed and i've learned more on Git... (?)2 -
When I do SSH to a remote server, how can I show git branch name?
When I SSH it shows me this:
admin@123.456.789.555:/home/some_folder$
Can I configure it to show something like oh-my-zsh that shows me the current Git branch I am pointed to?
This is my local iTerm zsh default theme:
some_folder git:(feature/some_branch_name)24 -
Trying to merge
A conflict was found, just small changes on both files
Trying to resolve
*A hour later*
Deleted the code form both branch, merged the branches and repushed the code to the merged branch.1 -
Would you guys be interested in a text editor saving system like in skyrim/fallout ? f5 saves current code by creating a new branch, f9 discards the branch and goes back to previous code and maybe f8 to merge.1
-
Sneaking a JavaScript code to open Kung fu panda scadush scene on logout :D never actually got merged to main branch (nor I would allow it) but got all the team giggling
-
Git cherry-pick 35 commits, another dev commit to the wrong branch, and these commits will be released first
-
Today's the day I realized my branch was better off if I just restarted from master and cherry-pick the commits I liked from the old one. This is what I get for the branch hanging around so long.
Lesson of the day: Merge early, and merge often. -
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 -
When someone tells you they have created a new branch with name "thisisMyNewBranchPleasePullToBeUptodate....."
and u have to type it2 -
i am switching jobs like a monkey switches trees. I never leave a branch before I grab the other one.1
-
When a major bug fixad recently by you reappears on production environment 'cause someone else (not you of course...) merged old branch content to live branch...
-
That feeling when you upgraded an internally used library from TypeScript 1.8 to 2.5 getting rid of the typings dependency and fixed its bug highlighted by the upgrade and all tests are green -- that feeling would not be rantworthy.
Realizing on trying to publish the new version that the master branch is not the actual master branch but a branch called 0.3 is. Of course I cannot merge my changes back there.
I don't mind a different main branch name. Yet don't call it a version, that's what tags are for. And for all that's holy, please set the proper main branch in your bitbucket / GitHub / gitlab so that I can find out easily.
Now I've wasted half a day and if you're looking for me: I'm gone searching for the motivation of doing the same shit again for the "main" branch. -
Every bloody time I work on a ticket and am about to be done... "git commit -av" Looking at the branch... Bloody hell, I am working again in master... Aborting commit. Checkout -b to a new branch... Committing... Going back to master... Merging my new branch into master... This exercise seems so pointless.
-
After three months of development, my first contribution to the client is going live on their servers in less than 12 hours. And let me say, I shall never again be doing that much programming in one go, because the last week and a half has been a nightmare... Where to begin...
So last Monday, my code passed to our testing servers, for QA to review and give its seal of approval. But the server was acting up and wouldn't let us do much, giving us tons of timeouts and other errors, so we reported it to the sysadmin and had to put off the testing.
Now that's all fine and dandy, but last Wednesday we had to prepare the release for 4 days of regression testing on our staging servers, which meant that by Wednesday night the code had to be greenlight by QA. Tuesday the sysadmin was unable to check the problem on our testing servers, so we had to wait to Wednesday.
Wednesday comes along, I'm patching a couple things I saw, and around lunch time we deploy to the testing servers. I launch our fancy new Postman tests which pass in local, and I get a bunch of errors. Partially my codes fault, partially the testing env manipulating server responses and systems failing.
Fifteen minutes before I leave work on the day we have to leave everything ready to pass to staging, I find another bug, which is not really something I can ignore. My typing skills go to work as I'm hammering line after line of code out, trying to get it finished so we can deploy and test when I get home. Done just in time to catch the bus home...
So I get home. Run the tests. Still a couple failures due to the bug I tried to resolve. We ask for an extension till the following morning, thus delaying our deployment to staging. Eight hours later, at 1AM, after working a full 8 hours before, I push my code and leave it ready for deployment the following morning. Finally, everything works and we can get our code up to staging. Tests had to be modified to accommodate the shitty testing environment, but I'm happy that we're finally done there.
Staging server shits itself for half a day, so we end up doing regression tests a full day late, without a change in date for our upload to production (yay...).
We get to staging, I run my tests, all green, all working, so happy. I keep on working on other stuff, and the day that we were slated to upload to production, my coworkers find that throughout the development (which included a huge migration), code was removed which should not have. Team panics. Everyone is reviewing my commits (over a hundred commits) trying to see what we're missing that is required (especially legal requirements). Upload to production is delayed one day because of this. Ended up being one class missing, and a couple lines of code, which is my bad (but seriously, not bad considering I'm a Junior who was handed this project as his first task at his first job).
I swear to God, from here on out, one feature per branch and merge request. Never again shall I let this happen. I don't even know why it was allowed to happen, it breaks our branch policies. But ohel... I will now personally oppose crap like this too...
Now if you'll excuse me... I'm going to be highly unproductive and rest, because I might start balding otherwise after these weeks... -
Think I'm gonna branch out from dev for a minute and try my hand mucking about with my arduino kit! Any cool ideas guys? Robot Arm seems to be my prevailing will so far4
-
First time I use Travis CI today :D
(And my first build error ever...)
In combination with Nuxt.js it is so fucking useful for Vue Development. Wow!
I think I've found my new favourite JS Framework.
Had a bit of trouble with Github Pages but I just created a 'source' branch with the source code and a 'master' branch with the deployed site. The reason is that organization sites can only be published from 'master' branch for some reason...
Anyways Travis CI is very useful!3 -
My heart was still full of excitement when my branch was merge in develop branch without any comment. 🤩🤩🤩
-
>add new feature, push to seperate branch
>ask other dev to have a look at code
>other dev completely rewrites the feature and pushes directly to master
please1 -
Current deploy process on the legacy project I'm on right now: ssh to server, check out branch with new feature, test on live, if it works then merge to master and check out master.
Oh... Oh no... -
Commit every change, all of them... Yes the "Forgot a ; " MUST be commit... Commit in the DEV branch... Because you aren't ready for the PRODUCTION branch... And backup every night after work...
-
I just started learning Norwegian. Does anyone know how I can enable branch prediction in the compiler?1
-
Me: Never check in code on Friday...
Me: Comes to work on Monday...
Me: WTF changed on Friday???
Always check-in at the end of each day on the dev branch! -
Sometimes I genuinely wonder what the thought process of some people is...
git checks out feature-X branch
git creates new branch off of it to work on something that has absolutely nothing to do with feature X
then opens a PR back into feature-X
Me: this has nothing to do with feature X.. i think you meant to branch off of develop and PR back into develop, no?
Them: no it was intentional .. feature-X will eventually end up on develop so I thought we'd get both features on develop.
I'm not even mad and this isn't a rant, I'm just really confused 🙂4 -
Use
git branch --merged
to get, you guessed it, all the branches you have merged.
Use
git branch -d <branch-name>
To delete a branch if it has been merged (use -D for forced)
And Use,
git branch --merged | egrep - v "(^\*|master|dev)" | xargs git branch - d
To delete all the branches that you have merged (but not anything with master/dev in their names)
Sorry for the formatting, I don't know how coder formatting works on DR..4 -
What branching methodology do you use and why? We've been using a trunk based development model, but I'm reviewing others.10
-
That moment when you go to merge a branch and realize no one rebased for 3 weeks and your whole day will be merge conflicts...1
-
EVEN THOUGH YOU PUSHED 31 FEATURE BRANCHES YOU'RE WORKING ALONE ONE YOU KEEP PUSHING CHANGES TO THE MASTER BRANCH. MOTHER OF GOD! WHY!?!?!?!?1
-
True horror story: DIBOL software produced by an outsourced team with one SVN branch per customer.1
-
To branch or not to branch? (in developing software multiple features, releases...) (git)
I've been searching a lot of posts and info on the internet ( http://bit.ly/2kBLcar http://bit.ly/197szRP ). In summary, some people say it is better to branch and others the opposite. What do you think?
My conclusion was: let's branch but let's merge periodically to minimize merge conflicts.1 -
"I'm gonna use your branch, you've done it better than we have it now"
https://i.imgflip.com/ggywy.jpg/...2 -
Git Merge 1 of branch to master: COMPLETE
Git Merge 2 of branch to master: (code change on branch, no change to master, exactly the same conditions, command, and procedure as before) FAILED - CONFLICT
Guess I’ll just die?3 -
Building. Building C++ takes so damn long. Accidentally checked out a wrong branch? Well there goes 20 mins.
-
A: oh hey my commit is not in the master branch...
A: *seeing bunch of commit deleted activity in bitbucket by B
A: Lol B deleted commits in master branch
B: Wait, what?! I know I have rebased my branch.. but never have I rebased anything in the master branch.. how can this be *intense breathing
B: Are you sure you have pushed yours to master?
A: Sure I've rebased, squashed, and rbt landed my work to master, here look my local master has my commit
CTO: wait what? Is this related to this bug we have in production just now? Please don't panic, let us resolve it
Turns out rbt land just squash your commit to your local master branch and they thus A have not pushed it to the remote. And the bunch of commit deleted activity were bitbucket not informing from which branch the activity was happening. Almost gave us heart attack. -
I find it really annoying when someone insists that the develop branch is for production and not... development...5
-
PM: let's show customer the new feature while it's still in the develop branch
Me: no fucking way this could ever happen -
Frustrated with solving the mess in master branch that cocky developers who don't understand git create.
-
How do you deal with situation when u need to merge multiple feature branches to develop branch? All feature branches have develop branch as base. So as soon as one feature is merged to develop then there will be contlicts in other feature branches.
Should I merge first feature branch to develop, then rebase feature2 branch on most recent develop and then merge the rebased feature2 branch to most recent develop and continue like that?
What if later I need to do hotfixes for previously merged branches? Should I revert them then rebase them on most recent develop and once again merge it to develop? Or should I just make small commits for fixes.10 -
Mondays are for branch cleanup! It's gotten a *little* out of hand...anyone else this unorganized from time to time?
1 -
Perforce just deleted all my work from yesterday and today. Apparently using the 'update branch mapping' feature is a bad idea3
-
I was about to implement a new feature (which I will call feature X), but I was not sure which branch feature X should be implemented on. Because of different products, there are a lot og branches around.
I was going to implement feature X on branch A, but that branch was currently not working, and someone was working on fixing it.
I was told by my boss to branch out from branch B as feature X would be merged in there later anyways.
And so I did.
After I am nearly finished with feature X I discover I need feature Y from branch A. Feature Y is not yet on branch B, but is scheduled to be merged in some time soon.
So I can't really finish feature X before that point, and I am told by colleague 1 I should have implemented feature X on branch C, because feature Y is there and branch C will be merged into branch B soon.
However, I found out that this has happened before.
First, colleague 1 was told to implement feature Y on branch A. This is the real implementation, the one I need. After he had spent a week implementing feature Y, he was told by colleague 2 that the feature should be implemented on branch C, which is branched off from branch B (I think). So he had to spend a day or two to move feature Y to branch C, but he still kept feature Y on branch A, because all branches will eventually be merged into branch A.
After a week or so, colleague 3 asks about feature Y and is told that the feature is on branch C. But colleague 3 need the feature on branch D, which is branched off branch B for some weeks ago.
I don't know all the details here, but colleague 3 ends up implementing a version of feature Y on branch D and he is happy.
I don't know how much time was wasted because of wrong information from management, but I have no intentions of wasting more time. I'll wait for the merge of branch C into branch B.
If this rant makes no sense, that's just my reflection of management some times.
I love management.4 -
When a junior developer forks new feature branch from his old feature branch and not from develop branch causing merge conflicts later!1
-
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 :(
-
You want to re-merge a branch after a previous merge has been reverted on the mainline branch?
That's easy! Just revert the revert commit and then merge again. Because logic. -
Question about managing git branches.
For releases, we branch develop (the main branch) into a release.version branch in which we bump the version and do any last minute bug fixes for issues found in testing.
After the release we need it back into the main branch as well as master.
But also we keep the branch as well in case we need it such as for a hotfix release.
Is keeping it right though?
General issue on my team I feel is nobody deletes their feature branches after they are done and merged into the main branch. I think there is a feature in most Repos where it can auto delete these branches when a PR is merged.
And well branches themselves (at least the HEAD) are sort of just bookmarks. All commits can be accessed by their hash and basically is a full snapshot of all the commits that upto that point that it was based off of?
So you could just tag the last commit in the release branch with release.version and delete the branch itself? And that I think is the correct, normal way?
Not sure how to explain this to my boss or team as they aren't big on technical details...9 -
Submodules in git.... every time you switch a branch on the main git repo the submodules end up going haywire2
-
Ok its been an hour now trying to find a way to push a NEW commit to a MERGED branch. SMH! Help gitlab!7
-
Was thinking of some missing features for everyone's favorite source control software:
git blame problems --all
git wtf this_branch
git just_do_it_ffs
git just_fkin_merge_it branch
git abort --mylife -
Somewhere Between Development Branch And Production Branch, We all grew up!
#Also_This_Camel_Casing_Shit_Doesnt_Leave_My_Hands -
Release build fails. Bad test was commented out on development branch but merged into release branch.
-
Convince the CEO of my small company to branch out to games because I am too inept to start a company of my own.2
-
REBASE BEFORE CREATING A PULL REQUEST
Especially if you've had to pull from main 7 times. No one has pulled from your branch, you have no excuse!7 -
How to set the up a stagging environment for a github branch in heroku.
Lets say i have a master branch and a dev branch. All the changes and updates first pushed to dev branch and after successful review and test in goes to master branch.
But the issue is as i'm following the gitflow of keeping the master branch always deployable.since my heroku app is linked to the master branch, when i try to test the dev branch in production environment of heroku,sometimes it breaks for some error.and at that time the sites goes down untill i redeploy the master branch as it's the stable version .So how do i test a branch in heroku production environment while also keeping the the site active with master branch. it that makes any sense 🤡 plz help3 -
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)4 -
Git questions: If several people have merged different features into a release branch but then some need to be "undone" how do you do it? I guess the merge/pull? Without being everything else?5
-
Is git a history of what happend or a list intentional changes?
Had this discussion with my boss. He said i shouldn't rebase my feature branch because it is too much hassle (I did some squashing and fixups). I should just commit on top and merge master into my branch.
What is your git philosophy?
Do you "own" a feature branch until you create the PR?6 -
For a small team (<= 7 people) working on a self-managed Gitlab instance ('Starter' subscription), is it better if each user keeps a fork of the project they work on (working on other branch than master) or have everybody work on the same fork (still, different branches)?
Also, squash commits on branch merging, yes/no and why?4 -
How to use git rebase when working with master and staging branch?
It might be a stupid question, but I really like the idea of creating a feature branch, work on it, if there are multiple commits squash them, rebase in top of master and then create a pull request from that branch to master.
It keeps the gut log pretty clean.
However, how would you do this, when not only working with a master branch but a staging/testing too?
Would you just rebase onto staging, merge to staging and when everything is fine, rebase onto master and merge again? Is there a netter way?6 -
People complaining about people pushing to master branch directly: can't you actually protect master from force pushes and have each PR reviewed? Why is that so difficult to understand?3
-
getting tons of fucking merge conflicts on rebasing remote branch with current master because that mockerfucking code review is still pending
-
It's extremely frustrating when a project is set up so that development, staging, and production reside on one branch.3
-
I have to integrate Branch.io journeys to a React PWA. Just started reading the docs and got a basic idea.
Just confused about how shall I add the web SDK in the React way.
Also, any explanations, tips, things-I-should-beware about branch?
[that is, if anyone's happened to have heared of it] -
Fuck. I created a branch from beta instead of our production branch. This is why I always check my commits before pushing...2
-
Had a new dev take us to merge conflict hell due to rebasing... we have meeting saying we are going to do git flow.....
manager who agreed makes branch project/releaseName based off of develop only to have us mr to that branch to then mr back to develop....
Had massive conflicts mr into that branch (i kept up to develop) and then had conflicts mr that branch to develop........ on a sunday night... great2 -
Have a question about git rebase with android studio.
So I have a feature branch which I finished working on, I made a pull request to develop branch and now I see many conflicts because develop is few commits ahead.
In android studio I switched to my feature branch, then did a git rebase develop and resolved all conflicts. After conflicted files were fixed I did a git add conflicted_file and continued with git rebase --continue until the end.
Now everything is finished. I have a local feature branch that was rebased to current develop, and I resolved all conflicts.
Problem is when I do a git push to my remote feature branch, I get a merge conflict error conflict from android studio and now I have to solve all merge conflicts yet again for some reason.
What I am doing wrong?2 -
How can you know my mood? Check my git commands. Am I using `git push -u origin SQUAD-feature-branch --force-with-lease` or `git push -f`?4
-
Git Question:
Semiunusual state here. Have a branch I'm trying to merge into develop and there are a LOT of merge conflicts, some head way has been made in this merge branch..
HOWEVER
I'm wondering is there a way to "suspend" the branch/merge progress and go back to develop?9 -
hey, how do you keep up with the migration files and git branches, i name them, how do you make sure the current branch has latest migration files so it does not break your application :)2
-
Anyone aware of an extension for VSCode that can create a branch from a task/issue in GitHub or GitLab; similar to how IntelliJ tasks work?1
-
Got flow idea : spawn 1 docker instance for each feature branch so the testing team can test each feature in isolation. Good idea or not?1
-
Did git go back to using “master” instead of the new “main” as its default branch name? Because when you create a new repo on GitHub now, they explicitly ask you to rename the branch to “main”. I checked by doing ‘git status’ on a newly initialized repository and it still shows “on branch master”.
3 -
yeah sure, having all 5 devs only ever working directly on the production branch and not being allowed to save anything post-release unless it's an urgent bugfix sounds like a great idea
-
Commenting and forgetting to delete before merging to master, only to create another branch just to delete these comments or put TODOs. 😑😑
-
Next year I have to decide what branch I'll be studying , I am between computing and software , I like security too, ¿ any help ?7
-
The smaller the code changes the longer the name of PR for the code.
And even more review changes mentioned by the reviewer... -
VPN -> SSH -> git clone -> git branch -> sshfs pull -> edit-> restart VPN/SSH every hour or so when it goes down -> sshfs push -> git commit -> git push -> fml
-
An intern wrote down in their timesheet:
Monday, 3 hours, "going over git commands to push code to <branch>"
3 hours my ass6 -
Merging two months of work from one SVN branch to another without touching the trunk. I now know what the 16th level of hell is.1
-
BitBucket has an option to delete the branch on merge which for most cases make sense.
But what about release branches? needs 2 merges for master and develop.10 -
God damn sourcetree.
You already annoy to use, now i have to deal with this stupid thing eat up my work
All my local commit in last 10 days, gone. because I just change from HEAD branch to master branch. WHY THE FCK YOU REMOVE IT.
GIVE ME BACK MY WORK!!!2 -
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