-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Writing PowerShell modules is fun but can be tedious to set up.
4 years ago I created this repo as a base that can be copped to create modules.
As I was setting up a new module (https://github.com/ili101/PartnerCustomerCommunity) I realized I didn't use my own template, this showed me it's not good enough. So I'm thinking of improving it in 2 ways:
New-ModuleTemplate
New-ModuleTemplate Cmdlet that is sort of a wizard for creating a new module. It will ask you for a name, and the components you will like to use and create it for you, no need to copy and configure manually.
Collaboration
Why write stuff from scratch, if better solutions are available? We can promote other good tools and make them accessible easily.
Those are the areas I was thinking you will be able to select if and what to use:
Git
- Init a repo for you.
Build
- https://github.com/PoshCode/ModuleBuilder.
- https://github.com/nightroman/Invoke-Build?
- Single psm1 file.
- ps1 files with psm1 file that "." load them.
GitHub
- Upload to GitHub for you https://github.com/microsoft/PowerShellForGitHub or https://cli.github.com/...
Test
- Pester basic setup.
GitHub Actions
- Create basic actions (maybe use https://github.com/ebekker/pwsh-github-action-tools?)
Azure Pipelines
- I have test running and publishing azure-pipelines.yml
Publish to the gallery.
- I have Publish.ps1
Help?
What other tools or best practices are there that can be included or replace the ones I made?
Do you like to help?