the difference between GistPad's 'Repository Management' and Github's Remote Repositorie #235
-
@lostintangent |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey! I built the repository management experience quite a while ago, before the Remote Repositories extension existed. That said, even now that Remote Repositories is released, there are a couple reasons why I'm planning to continue maintaining repo management in GistPad (at least for myself 😄):
Over time, if the gap between GistPad and Remote Repositories closes, then I'd definitely reconsider removing the repo management from GistPad. GistPad is definitely focused on gist management, but there are also numerous people that are using GistPad for managing their notes/journals/wikis/docs, which are more appropriately stored in repos. |
Beta Was this translation helpful? Give feedback.
Hey! I built the repository management experience quite a while ago, before the Remote Repositories extension existed. That said, even now that Remote Repositories is released, there are a couple reasons why I'm planning to continue maintaining repo management in GistPad (at least for myself 😄):
GistPad is optimized for supporting "companion" repos, that can be always available, regardless what workspace you have open. I use GitHub repos for docs, wikis, etc. and I prefer having access to those files at any time, without needing to launch a new VS Code instance to browse/edit them. GistPad also supports commit/push on save, as opposed to requiring a separate commit gesture. So GistPad a…