Matthew
@matthew
Is there a good practice for sharing code files across machines without committing to GitHub? I switch often between desktop and MacBook, and don't want to just commit "saving progress" constantly, but also I don't want to have to commit code before it's ready. maybe a good hardware drive with remote access?
10 replies
0 recast
8 reactions
Samuel ツ
@samuellhuber.eth
rsync to a shared server found Nextcloud to not be optimal due to .git dir having so many small files cc @rafi
2 replies
0 recast
2 reactions
FlexasaurusRex -◨-◨
@flexasaurusrex
can always work from a secondary branch.
1 reply
0 recast
2 reactions
Giuliano Giacaglia 🌲
@giu
Codespaces
0 reply
0 recast
2 reactions
bchow
@bchow
gc -m ‘wip’ & gp origin my-branch After pulling it down on your other machine, amend the commit or soft reset the commit before force pushing
0 reply
0 recast
1 reaction
pugson
@pugson
rsync
1 reply
0 recast
1 reaction
marbleheart
@marbleheart
if it’s personal repo, you can softly reset the latest “progress” commit after switching devices. still more convenient than the other ways
0 reply
0 recast
1 reaction
HH
@hamud
you can use rsync to keep the same directories in sync across different computers,
0 reply
0 recast
1 reaction
Steve
@stevedylandev.eth
If you use Zed you can ssh into remote repos which is pretty slick Or you can go hardcore and use ssh + tmux + neovim
1 reply
0 recast
1 reaction
derek
@derek.eth
one of the most talented programmers i know committed every ~15m with nonsensical commit messages. can always squash the commits to have the message be the content in your pull request when it’s ready
0 reply
0 recast
1 reaction
krystal
@theekrystallee
you can use a testing branch if all else fails but im interested to hear any alternatives solutions
0 reply
0 recast
0 reaction
