whyrusleeping
commented
6 years ago gx-go uw is an alias for gx-go rw --undo, and is the opposite of gx-go rw.
After making your changes to the linked package, you'll need to do a gx-go uw before publishing.
All this is a rather cumbersome series of steps and I think I might be missing something.
For now, that's what we have. I'm very keen on getting input from users on what would make a better process, so let me know what you think we can do to improve things
I'm looking for documentation that would help me with the scenario described below which focuses on the workflow of using gx with git to keep track of changes.
I've installed
go-ipfsand I want to work and update one of its dependenciesgo-ipfs-cmdsusing git, that is, being able to track down my work and push it to the corresponding repo. After downloading and installing all ofgo-ipfsdependencies (make install) I've proceeded to use thegx-go linktool to replace the plaingo-ipfs-cmdsgx version with the git version cloned from the repo (see https://github.com/whyrusleeping/gx/issues/161#issuecomment-374706397).At this point the
go-ipfs-cmdsdependency is linked to the cloned git repo and all its dependencies (as reported by git) have been updated to use gx, e.g.,This makes sense because I still want
go-ipfs-cmdsto use the same dependencies asgo-ipfs(because I'm testing it through the use ofgo-ipfs).I can now work on
go-ipfs-cmdsand make the necessary changes but when I want to commit those changes (and later push them) I'm going to need to undo the import path modifications, for that I'm guessing I need to usegx-go rw,gx-go rw --undoorgx-go uw(I haven't figured out which yet). After the commit if I want to keep working on the repo I'm going to have to rewrite the imports again (and restore them again to commit).All this is a rather cumbersome series of steps and I think I might be missing something (a gx concept, a gx-go command) that would help me smooth this workflow but I haven't found much information in the gx/gx-go READMEs related to this.