5 ms·
Why not just keep working? That next commit will work just fine without a central server.
by mattnewton 7y ago
Why not just keep working? That next commit will work just fine without a central server.
- dekhn 7y agomerging work with contractor right now...
- mattnewton 7y agoThat works too, believe it or not. Just add another remote and pull it.
- dekhn 7y agoI only coordinate my remotes through github. I don't use git in "decentralized mode".
- giggles_giggles 7y ago>
- hackmiester 7y agoA lot of people do that too.
- darkpuma 7y agoThat's not something you decide once at the beginning and get stuck with it. You can reevaluate that decision at any point and easily add more remotes to a git repo on the fly.
- dekhn 7y agoSo, uh, it's not clear what exactly people are expecting me to do here. Wire up my repo to my contractors temporarily (not even sure how I'd do that as i don't have access to their machines or filesystems) then detach when github is back (it's already back)?
- darkpuma 7y agoA single repo can have many remotes. Adding additional remotes does not prevent you from also using old remotes, nor do you ever have to remove a remote that you intend on using again in the future. Obviously it's a moot point for you now, but getting comfortable with how git remotes works is something that could pay dividends for you in the future.
- dekhn 7y agoI have multiple remotes already and know how they work. What I'm asking is, if github is down, and I don't have ssh or other access to my contractor's repo on their machine, what is my remote supposed to attach to? Also, the additional effort to manage multiple remotes is entirely nontrivial.
- deleted 7y ago[deleted]
- house9-2 7y agoI believe git was originally designed to share commits via email. Here is one of the top hits searching "git email patch" https://thoughtbot.com/blog/send-a-patch-to-someone-using-git-format-patch https://thoughtbot.com/blog/send-a-patch-to-someone-using-gi...
- modderation 7y agoThey can always tar up their repo and send it over. You then unpack it on your end, then set it as a remote, pushing/pulling from it as you see fit. Admittedly, not the greatest workflow, but it doesn't require any new tools if you are already familiar with remotes. As another alternative, git-format-patch/git-apply or git-bundle may be a quicker way of shipping changes around.
- darkpuma 7y agoYou don't need write access to a remote for that remote to be useful. Two or more people can collaborate using public repos that others may fetch from but not push to. Then, in lieu of github PRs, you request other people pull from you with email or however you like. If you need access control without VPNs or whatnot (or if you simply want something closer to the github workflow), there are other services similar to github that can almost certainly provide what you need, such as gitlab. > "Also, the additional effort to manage multiple remotes is entirely nontrivial." With practice, I'd say it asymptotically approaches trivial.
- ilikehurdles 7y agoAt some point there has to be centralization. We are deploying one product, not N products for N commits. If I can't push, I can't have CI build my branch, and I can't submit a PR for review.
- inflatableDodo 7y agoIt should be easy to move the center. Having a single 3rd party be the only central point you have available is asking for trouble.
- mbrumlow 7y agoBut you could continue working and only have to apply minor patches forward if you later find your starting point needed to be fixed. You don't have to wait for CI, just create a new branch and continue your work as though CI passed, and your PR was accepted. If that comes true you don't need to worry much, just rebase and continue. On the other hand if you find out you needed to make changes - do those on the branch you made those changes, and finish your PR/CI cycle. Then go to the new branch you continued work on and rebase, and continue. Is there something I am missing?
- harel 7y agoBecause we forget how to let go of all this work stuff and get sucked into it. There is a life out there too. some one us can balance, some find it hard. this is an opportunity to just pause for a few minutes. Mentally pause.
- deleted 7y ago[deleted]
- nickthemagicman 7y agoRight. There's an entire world out there of of personal projects and open source contributions you can be doing when not working. People get so caught up in their daily coding they forget about all the other fun coding they could be doing outside of work. It's a shame.
- rv-de 7y agoOf course, you know that, I know that, we all know it - but our bosses don't ;)
- harel 7y agoThey are living in the technical stone age then. Time on keyboard does not equate good productivity. Happiness, balance, freedom - that increases output.
- partiallypro 7y agoBecause programmers always need a break. Don't go giving our bosses ammo. It's compiling, it's uploading, Github is down. Have some compassion.