possumbilities

@Murdock9803 Based on that I'd say work in the following PRs resolves this, closing. * #302 * #304 * #315

@nandu-99 feel free to give it a try and Issue a PR against the repo. If its accepted and merged we'll assign you :)

@Dev-JoyA You would need to fork the repository first, and push to your fork and open a Pull Request. There are others who have run into this in the Slack....

@egbadon-victor I like your approach, and I think its worth pursuing! I believe you created a duplicate issue on the vocabulary repo here: * https://github.com/creativecommons/vocabulary/issues/306 The original Issue: * https://github.com/creativecommons/vocabulary/issues/1...

Thank you for the detailed issue! ❤️ However, solutions likely lie further up the chain of changes in Vocabulary itself. I'm setting this as blocked, until such time as an...

@dijitali after considering this, I'm thinking the best option you've outlined is likely just `disable all git-hooks and leave code linting/formatting to be a manual step`. It's a tradeoff for...

> Yep, makes sense I think 👍 > > Am aware that this repo is due/blocked for a major upgrade (#356) which would perhaps negate the fiddly docker requirements. >...

Hi @RonaldRonnie Please put the the PR template information back and fill it out, rather than deleting it. Please also remove the changes you've made to the `package.json` file, they're...

@RonaldRonnie You can get the link by starting the creation of a new PR, and copying it from there before submitting it. In the future, please fill it out, rather...

Closing as this still doesn't follow the PR template, please feel free to submit a new PR in the future