You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This utility would be perfect to manage my shared dependency, if only had an option to use git's subtree (or clone, if target directory is not part of a repository) instead of fetch. Bonus point if look of subtree repo has been forked by principal repo user, and ask change the push remote.
The advantage of this system is to make easier to share the modification to the library between collaborator, but also to make easier to make pull-request.
The repository should be created in a way they are good to be directly cloned; just code, licence, README.md, and the package.json.
The test code can be placed in a different repository, witch obviously add the "code repository" as submodule dependency
This utility would be perfect to manage my shared dependency, if only had an option to use git's subtree (or clone, if target directory is not part of a repository) instead of fetch. Bonus point if look of subtree repo has been forked by principal repo user, and ask change the push remote.
The advantage of this system is to make easier to share the modification to the library between collaborator, but also to make easier to make pull-request.
The repository should be created in a way they are good to be directly cloned; just code, licence, README.md, and the package.json.
The test code can be placed in a different repository, witch obviously add the "code repository" as submodule dependency
this is what i do for my project, see https://github.com/MauroMombelli/FreeDCM_test
Edit: found out subtree are more appropriate than submodule
The text was updated successfully, but these errors were encountered: