-
Notifications
You must be signed in to change notification settings - Fork 22
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
Update dependencies so build passes #8
base: master
Are you sure you want to change the base?
Conversation
6098d48
to
b5111f0
Compare
IIUC the build/ci failure is expected due to the way GitHub actions are setup in this repo. My fork won't have access to this repo's tokens as required by the github action. |
@jwgmeligmeyling - Hello and thank you for your work on this project. Are you actively maintaining this project, and are you willing to merge this PR? |
Hi @Scottmitch , thanks very much for your contribution! I am intending to continue to support it, but as I am also working on Blaze-Persistence, QueryDSL and Hibernate at the same time I can be incredibly busy... Honestly I just got the plugin to the point where I needed it to be for my own projects. I am a bit surprised about the traction it managed to get in this short time. I am definitely willing to integrate your PR's though. I've noticed that the |
Its been a while since I have looked at this PR, but seems like a permissions issue |
I looked through the security settings and I can't seem to find it. Is this kind of integration not supported at all for PRs from forks? |
…_yarn/node-fetch-2.7.0 Bump node-fetch from 2.6.2 to 2.7.0
No description provided.