Note: the "Coverage Target" badge above reflects the 80% goal checked in ci.yml; the workflow currently emits a warning when coverage falls below that threshold rather than failing the build, so it is a target, not a hard-enforced gate.
TicketManager is a tool for managing GitHub Issues through GitHub Projects. It lets a user switch between GitHub Projects and manage that project's issues (create, update, triage, view) without leaving the app. GitHub itself is the system of record — there is no local database or persisted copy of issue data. See docs/ARCHITECTURE.md for the full architecture and technology stack.
Current implementation state: this repository is an early-stage .NET Aspire / Blazor application. src/Web includes a Home overview page, a GitHub Projects dashboard page, and an About page, styled with Tailwind CSS — GitHub Issues create/update/triage workflows are not yet implemented.
- .github/workflows — canonical CI/CD, lint, triage, sync, and release automation workflows.
- .github/hooks — local hook scripts (including pre-push gates).
- .github/instructions — coding and documentation instructions applied to contributors and agents.
- src/AppHost — .NET Aspire orchestration project that composes and launches the app's services for local development.
- src/ServiceDefaults — shared Aspire service-defaults (telemetry, health checks, resilience) referenced by other src projects.
- src/Web — the Blazor UI project (Home, GitHub Repositories dashboard, and About pages, styled with Tailwind CSS).
- tests/AppHost.Tests — integration tests for the AppHost orchestration project.
- tests/Architecture.Tests — architecture/convention tests enforcing project boundaries.
- tests/Web.Tests.Unit — unit tests for the Web project.
- tests/Web.Tests.Bunit — bUnit component tests for Blazor components in Web.
- tests/Web.Tests.Integration — integration tests for the Web project.
- tests/Web.Tests.E2E — Playwright end-to-end tests against the running Blazor UI.
- All of the above are wired into TicketManager.slnx.
- docs — architecture, contribution guidance, and release-review history.
- Directory.Packages.props, global.json,
GitVersion.yml, and NuGet.config — shared
dependency/version governance;
NuGet.configrestricts restores to nuget.org as the sole package source, with package source mapping.
- Docs landing page — overview and documentation entry points.
- Architecture overview — repository layout and policy boundaries.
- Contributing guide — contribution workflow and validation expectations.
- Release review blog index — release-review post index.
The release review posts in docs/blogs summarize the rollout history of workflow-standard and major changes by release.
- Review the standard and policy surface in .github/workflows, .github/hooks, and .github/instructions.
- Copy the assets you want to adopt into your target repository.
- Validate in CI and locally with the same gates this repo uses
(workflows in
.github/workflows, hook behavior in.github/hooks/pre-push). - Track updates through releases and release-review posts in docs/blogs.
-
Clone and restore:
git clone https://github.com/mpaulosky/TicketManager.git cd TicketManager dotnet restore TicketManager.slnx -
Run baseline validation:
dotnet build TicketManager.slnx --configuration Release dotnet test TicketManager.slnxtests/Web.Tests.E2Erequires the Playwright browser binaries to be installed first, or its tests will fail. After building, install them with:pwsh tests/Web.Tests.E2E/bin/Debug/net10.0/playwright.ps1 install(adjust the path if you built a different configuration). -
Follow the full contribution workflow in docs/CONTRIBUTING.md.
The Release workflow runs when a PR
is merged to main (or by manual dispatch with a merged PR number).
Every merged PR to main is treated as release-eligible. The workflow runs one
release/blog pass per PR (idempotency marker: Source PR: #<number> in release
notes) and then:
-
computes semver bump from PR labels, with idempotency checks to avoid duplicate releases,
-
generates a release-review post and rebuilds docs/blogs/README.md,
-
updates this README latest-blog block (``) from
docs/blogs/README.md(top 5 rows), -
updates docs/index.html latest blog links from the same rows.
| Version | Date | Title | Blog post |
|---|---|---|---|
| v0.0.117 | 2026-11-11 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.116 | 2026-11-10 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.115 | 2026-11-07 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.114 | 2026-10-31 | chore(baseline): Re-apply the repo-ci-baseline Template | Post |
| v0.0.113 | 2026-10-26 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.112 | 2026-10-26 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.111 | 2026-10-26 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.110 | 2026-10-26 | chore(sandcastle): Add GATE_SCRIPT and CHECK_PATHS to the repo config | Post |
| v0.0.109 | 2026-10-26 | chore(sandcastle): Add the names the local review reads and deny Claude Code the ledgers and credential files | Post |
| v0.0.108 | 2026-10-25 | chore(sandcastle): Migrate to the Baseline Template's full pipeline | Post |