Fossil Forum
Post: Is it possible to set up a persistent "default" remote?
I've been learning about using multiple remotes (another phase of my move away from chiselapp fossil hosting). I now have "Remote O" (= oracle) which I think of as my primary or "default" (in my head!) remote, and "Remote C" (= chisel) which I'm maintaining simply by way of "backup".
My workflow has been to sync with oracle on each commit, and only occasionally to push to chisel. Of course, every time I push chisel, the fossil default updates to point at chisel, and I need to use fossil remote REF to point it back at oracle.
Is there any way to persuade fossil to keep oracle as the "persistent" remote, so that push to a different remote won't displace that?
I have a feeling I've answered my own question already, but ask on the off-chance that there may be a workaround, or perhaps I've missed something. Thanks!
fossil push --once C
fossil push --once C
So simple. :) I went right past that in the docs. Thanks!