Title: feat: add reusable CI and release workflows by HeyItsGilbert · Pull Request #5 · PowerShellOrg/.github · GitHub
Open Graph Title: feat: add reusable CI and release workflows by HeyItsGilbert · Pull Request #5 · PowerShellOrg/.github
X Title: feat: add reusable CI and release workflows by HeyItsGilbert · Pull Request #5 · PowerShellOrg/.github
Description: Stack position: 5 of 7 Two reusable workflow_call workflows. These are the shared CI/CD infrastructure that Plaster and PSDepend will adopt immediately after this PR merges. What's in this PR powershell-ci.yml (reusable): Matrix: Windows/Ubuntu/macOS × PS 5.1 (Windows only) + PS 7.x = 4 legs total NuGet provider bootstrap step for PS 5.1 before module install Installs: psake, PowerShellBuild, PSScriptAnalyzer, Pester 5 (pinned to 5.0–5.99) Fixed psake task sequence: Init → Test → Analyze Uploads test result artifacts per matrix leg (testResults.xml) powershell-release.yml (reusable): Inputs: module-name (required string), create-github-release (bool, default true) Required secret: PSGALLERY_API_KEY Runs full CI gate (Init → Test → Analyze) before Build → Publish Creates GitHub Release with auto-generated notes via gh release create --generate-notes Release runs on windows-latest only (publish from Windows for maximum compatibility) Consuming repo usage: # ci.yml jobs: ci: uses: PowerShellOrg/.github/.github/workflows/powershell-ci.yml@main # release.yml (tag-triggered) jobs: release: uses: PowerShellOrg/.github/.github/workflows/powershell-release.yml@main with: module-name: PSDepend secrets: PSGALLERY_API_KEY: ${{ secrets.PSGALLERY_API_KEY }} Council questions Pester version pin (5.0–5.99): intentional — keeps us on Pester 5.x and excludes a hypothetical Pester 6 that might be breaking. Agree? Release runs Windows-only: Publish-Module is most reliable from Windows. Any objection? --generate-notes for GitHub Releases: this pulls from PR titles since last release. Only useful once PRs are the standard workflow. For the first release, maintainers should write notes manually. Should we document this caveat? Init task in CI: this assumes every repo has an Init psake task. If a repo doesn't define it, CI will fail. Is the org wiki the right place to document required task names, or should we add a REQUIRED_TASKS.md here? Base: pr/04-templates — merge PRs 1–4 first.
Open Graph Description: Stack position: 5 of 7 Two reusable workflow_call workflows. These are the shared CI/CD infrastructure that Plaster and PSDepend will adopt immediately after this PR merges. What's in this PR p...
X Description: Stack position: 5 of 7 Two reusable workflow_call workflows. These are the shared CI/CD infrastructure that Plaster and PSDepend will adopt immediately after this PR merges. What's in this ...
Opengraph URL: https://github.com/PowerShellOrg/.github/pull/5
X: @github
Domain: github.com
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /:user_id/:repository/pull/:id/files(.:format) |
| route-controller | pull_requests |
| route-action | files |
| fetch-nonce | v2:da69749d-287e-a497-eabc-d18c05a3ee81 |
| current-catalog-service-hash | ae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b |
| request-id | CD36:238D17:90CDD3:C899D3:6AFD351D |
| html-safe-nonce | d127271fc2bd7e752f7c5788bf7f24cbead2b63ee6232829c06d3d08e5e7db20 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDRDM2OjIzOEQxNzo5MENERDM6Qzg5OUQzOjZBRkQzNTFEIiwidmlzaXRvcl9pZCI6Ijg3MjIzMjgyMjc3MDk1MzE0MjEiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 62cc393fae1e1a73ee4fb93c229ca0697769dab11764dcbc8096f0dadceecf4b |
| hovercard-subject-tag | pull_request:3564243803 |
| github-keyboard-shortcuts | repository,pull-request-list,pull-request-conversation,pull-request-files-changed,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/PowerShellOrg/.github/pull/5/files |
| twitter:image | https://avatars.githubusercontent.com/u/615265?s=400&v=4 |
| twitter:card | summary_large_image |
| og:image | https://avatars.githubusercontent.com/u/615265?s=400&v=4 |
| og:image:alt | Stack position: 5 of 7 Two reusable workflow_call workflows. These are the shared CI/CD infrastructure that Plaster and PSDepend will adopt immediately after this PR merges. What's in this PR p... |
| og:site_name | GitHub |
| og:type | object |
| hostname | github.com |
| expected-hostname | github.com |
| None | 065128366c233a9d57ff68ab6c96e25b99dd1b0ab70d23b70873d3dd6b5e4f19 |
| turbo-cache-control | no-preview |
| diff-view | unified |
| go-import | github.com/PowerShellOrg/.github git https://github.com/PowerShellOrg/.github.git |
| octolytics-dimension-user_id | 4895314 |
| octolytics-dimension-user_login | PowerShellOrg |
| octolytics-dimension-repository_id | 1217182813 |
| octolytics-dimension-repository_nwo | PowerShellOrg/.github |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1217182813 |
| octolytics-dimension-repository_network_root_nwo | PowerShellOrg/.github |
| turbo-body-classes | logged-out env-production page-responsive full-width |
| disable-turbo | true |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 941021edf0c2ec58298f4a2c8f27ae507d129c92 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width