The package can be found here:

https://community.chocolatey.org/packages/notepadplusplus-plugin.template

If this goes ahead, we could then remove the source files from this repository:

https://github.com/Davis8988/notepadplusplus-plugin-chocolatey-package-template

Is there an issue open for this already?

My suggestions would be templates for the following cases:

• Portable .zip
  Doesn't contain installers. Include a way to create shortcuts for the start menu. Create an .exe.gui.
• Portable .exe
  Not an installer. Create start menu shortcut. Create .exe.gui
• Zipped installer
  Contains setup.exe and maybe other stuff. Deals with unpacking to a directory (best would be the lib package directory and not C:\Users\username\AppData\Local\Temp since there were issues with paths with usernames containing non-latin letters) and removing unpack-directory afterwards.
  According to our discussion here: https://gitter.im/chocolatey/choco?at=55e87aaf05f4097b40f6c36a it should contain Get-ChocolateyWebFile Get-ChocolateyUnzip and Install-ChocolateyInstallPackage
• Normal installer
  Non-zipped setup files.

Might add more if I come up with something reasonable.

As an addition:
https://groups.google.com/forum/#!topic/chocolatey/bsmtXIV4e5g

NOTE: This was originally created by @aronovgj here, but the issue has been re-created here.

Add a GitHub action that builds, installs and tests available templates in the repository.

This action should run on every pull request and commit.

Steps that are action needs to do.

1. Build all template packages in the repository
2. Install all built packages
3. Run all Pester Unit Tests
4. Report status on the pull request

The package can be found here:

https://community.chocolatey.org/packages/msi.template

Once complete, we can remove the source files from this repository:

https://github.com/ferventcoder/chocolatey-packages

It would be nice to have a template similar to the built-in template but without help comments, as experienced package maintainers already know the information contained in them. Having these comments can just create unnecessary backspacing/deletion.

Possible names I thought of:

• slim
• advanced
• no-comment
• default-slim

Originally suggested by @bcurran3 in this issue: chocolatey/choco#1366

It would be useful to have some kind of automation that allows us to build, test and push templates to the community repository.

My idea is to add a GitHub action that can be triggered manually whenever there is a need to push packages.

This action should go through the steps.

1. Build the templates that are needed to be pushed
2. Install these templates
3. Run unit tests for these packages
4. Push the templates to community.chocolatey.org using the Chocolatey Community maintainer.

The package can be found here:

https://community.chocolatey.org/packages/zip.template

Once complete, we can remove the source files from this repository:

https://github.com/ferventcoder/chocolatey-packages

To make it clear on community.chocolatey.org that these packages are part of the building blocks for using Chocolatey to create packages.

@TheCakeIsNaOH @AdmiringWorm I am not an artist/designer, so this is not something that I would be able to come up with. But perhaps @designxsteph might be able to help here?

The package can be found here:

https://community.chocolatey.org/packages/vscode.template

Once complete, we can remove the source files from this repository:

https://github.com/AdmiringWorm/chocolatey-packages

/cc @AdmiringWorm