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
On Dec 7, 2016, at 12:31, Ripley511 ***@***.***> wrote:
This is quite annoying: I have a project where the repo contains java back-end sources and the front-end sources in a separate folder, like so:
.
|____.git
|____project-backend
|____project-scripts
|____project-ui
| |____node_modules
| |____package.json
|____project-webapp
Is there any way to tell pre-git to look for package.json in a specific folder? If not can we add this feature? I'm up for it :-)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
We have to assume the user pwd can be anywhere from the deepest to the root folder of his git repository. Once we find the root (cd.. until pwdis equal to GIT_ROOT), we scan every sub-folder in the root folder for a file named 'package.json', cd to that folder and run the hook commands.
Does this solution make sense?
You may even find situations where several sub-folders contain a package.json, each with different commands associated to their git-hooks. It might be complicated though not impossible, in my opinion, to run individual scripts for each of them (but this is another subject).
This is quite annoying: I have a project where the repo contains java back-end sources and the front-end sources in a separate folder, like so:
.
|____.git
|____project-backend
|____project-scripts
|____project-ui
| |____node_modules
| |____package.json
|____project-webapp
Is there any way to tell pre-git to look for package.json in a specific folder? If not can we add this feature? I'm up for it :-)
The text was updated successfully, but these errors were encountered: