Closed crguezl closed 2 years ago
I don't fully understand. config.json doesn't belong to the repo anymore. Now when the user execute any command the program create a fresh config in case it doesn't exists. Which is more likely to happen in the first execution
OK. Seems my version was rusty.
✗ git ls-files config.json
config.json
I see in the new version it is removed
Ya veo que ha cambiado bastante
@GGCristo
When a user upgrades
gh-edu
to the last version with s.t. likegh instal gh-edu
, since the fileconfig.json
belongs to the repo and more than likely the user has changed theconfig.json
with organizations info, etc. conflicts may arise.It seems that
config.json
is an independent file and must be stored in a different user repo?