New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not executing on bundle install #1
Comments
Update: Changing my Gemfile to point to this repo seems to work. My guess is that the released gem has a bug in it and requires updating. |
Hmm, interesting. This required a ton of testing to get it to work, and so I tested it by pointing to the repo rather than pushing a gem. I wonder if Bundler behaves slightly differently depending on where the gem comes from… I'll play around with it and see what I can figure out. |
Maybe ¯_(ツ)_/¯ I was trying to debug the gem itself so I cloned it from GitHub and changed my Gemfile to use my cloned versions This is when I changed it to point to GitHub to test which again seemed to work just fine. After this I had just assumed the published Gem was outdated. |
Hmm, OK, so if you're manually running the code in the Which leaves the problem of why |
Also, I'm amazed you found this 😂 I was waiting to tell anyone about it until I'd confirmed it worked consistently. |
I know right? I searched I wanted something like the I then searched for |
So it turns out this 🔮 dark magic 🔮 can be quite scary... Looks like it's broken deploys for us on Heroku. I'd suggest finding a way of making this run without
|
Ruh roh! Hmm… would this be solved by putting in the |
First of all ❤️ the idea of this project, and is exactly what I am after. However, I'm not seeing it behave as documented.
I am finding that the script is not being executed on
bundle install
, but works perfectly if I invoke it withbundle exec git-hookshot
.It seems perhaps
pre_install
is not being executed or something is up with theoutput
.When I run the following in
irb
thenoutput
is an empty string. I do get the symlink created though.I am running ruby
2.4.1
with bundler1.15.1
.I've got an open PR here exhibiting this issue.
The text was updated successfully, but these errors were encountered: