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
Originally created by @cjohnhanson on 2022-04-05 20:02:43
Before commit:
Changed files should be linted
Local branch being committed to should be up to date with master in this meltano/handbook repo
We would need to either just fail with an informative warning if branch isn't up to date or if we wanted to automatically pull, we would need to be smart about that behavior--how should it merge? What happens if a pull would overwrite local changes?
We can probably do this by:
Creating a new .githook directory with a precommit script
Adding a preinstall script in package.json which does a git config core.hooksPath .githooks so that precommit hooks are "installed" whenever npm install is run.
The text was updated successfully, but these errors were encountered:
Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/82
Originally created by @cjohnhanson on 2022-04-05 20:02:43
Before commit:
master
in thismeltano/handbook
repopull
, we would need to be smart about that behavior--how should it merge? What happens if a pull would overwrite local changes?We can probably do this by:
.githook
directory with aprecommit
scriptpreinstall
script inpackage.json
which does agit config core.hooksPath .githooks
so that precommit hooks are "installed" whenevernpm install
is run.The text was updated successfully, but these errors were encountered: