update new tool issue template

- add `Tool_Group` to class names
- update `master` to `main` and no longer instruct to use `dev` branch
- add tip to copy-paste from another tool

Author: owlang

.github/ISSUE_TEMPLATE/new-tool.md

@@ -13,19 +13,21 @@ assignees: ''
 
 ## Checklist
 
-New tools should be written on branches off `dev`. A pull request to the `dev` branch can then be submitted and a reviewer will review the code and accept the merge.
+New tools should be written on branches off `main`. A pull request to the `main` branch can then be submitted and a reviewer will review the code and accept the merge.
 
-- [ ] Write tests
+- [ ] Write **tests** for Github Actions (automatic testing)
 - [ ] Write tool (list changed files)
   - [ ] `objects.ToolDescriptions.java`
-  - [ ] `scripts.MyTool.java`
-  - [ ] `cli.MyToolCLI.java`
-  - [ ] `window_interface.MyToolWindow.java`
-  - [ ] `window_interface.MyToolOutput.java`
+  - [ ] `scripts.Tool_Group.MyTool.java`
+  - [ ] `cli.Tool_Group.MyToolCLI.java`
+  - [ ] `window_interface.Tool_Group.MyToolWindow.java`
+  - [ ] `window_interface.Tool_Group.MyToolOutput.java` (Optional)
   - [ ] `main.ScriptManagerGUI.java`
   - [ ] `main.ScriptManager.java`
 - [ ] Add logging support
 - [ ] Update documentation (docusaurus)
-- [ ] Write Galaxy wrapper
+- [ ] Write **Galaxy wrapper**
 
 Then you can pull your changes into master! 🎉
+
+### Developer tip: Copy-paste source code from a similar tool in scriptmanager for the implementation