Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/codaamok/test123
https://github.com/codaamok/test123
Last synced: 26 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/codaamok/test123
- Owner: codaamok
- License: gpl-3.0
- Created: 2021-11-09T10:21:43.000Z (almost 3 years ago)
- Default Branch: master
- Last Pushed: 2021-11-09T19:04:48.000Z (almost 3 years ago)
- Last Synced: 2023-08-20T23:38:34.178Z (about 1 year ago)
- Language: PowerShell
- Size: 76.2 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# test123
My PowerShell pipeline build module## Folders
### Files
Store all additional files to include as part of the module manifest property `FileList`.
### ScriptsToProcess
Store all scripts to process as the module manifest property `ScriptsToProcess`. Any .ps1 script files defined within this directory will be merged into a single Process.ps1 during build.
## To Do
- Write blog post on how to develop modules using this helper module
- Add comment based help
- Flesh out `New-ProjectDirStructure`
- Include vscode tasks.json and launch.json
- Auto-updater in GitHub Actions workflow for build script and workflow yaml
- Fail the workflow if there are newer files in the module compared to the repo, and force user to create an ignore file or update the files?
- Make fewer assumptions about GitHub Actions being the build platform
- Perhaps define module name and author using vscode workspace env vars
- Handle the GitHub project automatic links
- Assumption made on always using GitHub Actions in `Update-BuildFiles`