Source Control for Chocolatey Packages: Because Future You Deserves Answers
summary
Argues that packaging files belong in Git so history, signed commits and PR review show who changed what and why; demonstrates an update.ps1 with Chocolatey AU that fills version and URL, a simple Pester suite kept in tools then excluded via exclude tests from package, and a CI flow that runs on a self-hosted GitHub Actions runner to create nupkgs and push to ProGet; the example is built, tested, merged and shown to work end to end.
AI-written summary · about
chapters (7)
- 0:00Source control for Chocolatey
- 1:15Why source control matters
- 3:46Live demo: Chocolatey repo
- 14:56Maintaining packages with reviews
- 27:04Pull requests for updates
- 30:37Automating with GitHub Actions
- 40:34Advanced automation & Q&A
related talks
47mLess Clicking, More Sipping - How Chocolatey for...
35mOptimizing Chocolatey Packages for Others
49mChocolatey For the Organizations: Easily Manage Software
55mTransforming Software Management with Chocolatey for Business
49mStreamlining Software Management with...
30mSource Control for IT Pros
30mCompletely Automate Managing Windows Software...Forever
44mA Real-World Look at Package Management Tools