Add issue template & automation for Node tools installed with npm #1046
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ana06
changed the title
Ana06
added
💎 enhancement
Add `NODE` template to the `create_package_template.py` script.
Add new issue template to propose the addition of a new package/tool that is installed from the JavaScript Package Registry installed with `npm install -g <tool_name>`. The new issue template supports the `send PR` automation to create new packages automatically. Improve and keep consistent the other _new package_ templates.
|
Created issue for the idea mention above: #1047 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add new issue template to propose the addition of a new package/tool that is installed from the JavaScript Package Registry installed with
npm install -g <tool_name>. The new issue template supports thesend PRautomation to create new packages automatically using the newNODEtemplate. Improve and keep consistent the other new package templates.In addition, we could add to the existent NEW PACKAGE from URL template Node packages installed with npm from a URL (such as GH repos). For this we can use the
VM-Install-Node-Tool-From-Zipfunction. But it is a bit more complicated to implement than this case, as we would need to add an extraargumentsorcommandparameter to the script and the template. This would be an improvement for the current package types as well. I suggest tracking this as a new issue and implementing it in multiple steps: addargumentsparameter to scrip + current template, and then add to the existent NEW PACKAGE from URL template Node packages installed with npm from a URL.You can see it working in Ana06#27
Closes #999