Public Notes by chase_ats Tagged #version_control
Notes publicly shared by our members.
By the current Highrise CEO. Seems pretty beast. Too bad it's not updated too much and not an app or anything. Dropbox Paper apparently needs you logged in. Quip has similiar issues sort of (even if not need logged in, app is the focus). DraftIn is a bit too minimal perhaps and not wiki-ish.show more
"This something I’ve been using for quite a while without bad consequences and suggested by Linus Torvalds on the git mailing list. araqnid’s solution is the proper one for bringing code into your repository… but when you, like me, have multiple equivalent authoritative upstreams (I keep some of my more critical projects cloned to both a private upstream, GitHub, and Codaset), it can be a pain to push changes to each one, every day. Long story short, git remote add all of your remotes individually… and then git config -e and add a merged‐remote. Assuming you have this repository config: [remote "GitHub"] url = email@example.com:elliottcable/Paws.o.git fetch = +refs/heads/*:refs/remotes/GitHub/* [branch "Master"] remote = GitHub merge = refs/heads/Master [remote "Codaset"] url = firstname.lastname@example.org:elliottcable/paws-o.git fetch = +refs/heads/*:refs/remotes/Codaset/* [remote "Paws"] url = email@example.com:Paws/Paws.o.git fetch = +refs/heads/*:refs/remotes/Paws/* … to create a merged‐remote for "Paws" and "Codaset", I can add the following after all of those: [remote "Origin"] url = firstname.lastname@example.org:Paws/Paws.o.git url = email@example.com:elliottcable/paws-o.git Once I’ve done this, when I git push Origin Master, it will push to both Paws/Master and Codaset/Master sequentially, making life a little easier."show more
30-day, hassle-free money back guarantee For aspiring senior developers looking for battle-tested best practices, a killer community, and mentorship from the right people. #iOSshow more