GitHub-native by design
TicketManager centers GitHub Projects and GitHub Issues instead of mirroring them into a separate backing store.
Read the architecture guideTicketManager is a developer-focused app for working with GitHub Issues inside GitHub Projects while keeping GitHub itself as the system of record. The repo is early in its journey, with a clean Aspire scaffold, a Blazor front end, and strong docs-first engineering habits.
From architecture rules to test scaffolding and release notes, the project is building a tight loop between product intent, implementation, and documentation.
TicketManager centers GitHub Projects and GitHub Issues instead of mirroring them into a separate backing store.
Read the architecture guideThe front end is being shaped as a modern Blazor experience with Aspire orchestration and strong shared defaults.
Browse source projectsRecent write-ups explain what shipped, why it mattered, and how the repository is evolving.
Open the blog archiveThe newest releases, written into this page by the release workflow each time one is published.
| Version | Date | Title | Blog post |
|---|---|---|---|
| v0.0.104 | 2026-10-18 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.103 | 2026-10-18 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.102 | 2026-10-18 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.101 | 2026-10-18 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.100 | 2026-10-18 | chore(deps): Have Dependabot ignore claude-code-action | Post |
| v0.0.99 | 2026-10-18 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.98 | 2026-10-18 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.97 | 2026-10-18 | chore: Re-apply the repo-ci-baseline Template | Post |
| v0.0.96 | 2026-10-16 | build(deps): Update NuGet packages | Post |
| v0.0.95 | 2026-10-16 | build(deps): Fail restore on vulnerable NuGet packages | Post |
The newest release posts from docs/blogs/, written into this page by the release workflow.
Re-Apply the repo-ci-baseline Template so this repo carries the Template changes from mpaulosky/dotfiles#219, mpaulosky/dotfiles#226, mpaulosky/dotfiles#228, mpaulosky/dotfiles#229…
Re-Apply the repo-ci-baseline Template so this repo carries the Template changes from mpaulosky/dotfiles#219, mpaulosky/dotfiles#226, mpaulosky/dotfiles#228 and mpaulosky/dotfiles#229.
Re-Apply the repo-ci-baseline Template so this repo carries the Template changes from mpaulosky/dotfiles#219, mpaulosky/dotfiles#226, mpaulosky/dotfiles#228 and mpaulosky/dotfiles#229.
Re-Apply the repo-ci-baseline Template so this repo carries the Template changes from mpaulosky/dotfiles#219 and mpaulosky/dotfiles#226.
The repo-ci-baseline Template pins anthropics/claude-code-action to the version that claude-review.yml's sandbox notes were checked against: the Read restrictions on symlinks, .. and .git, and…
Re-Apply the repo-ci-baseline Template so this repo carries the Template changes from mpaulosky/dotfiles#176, mpaulosky/dotfiles#178, mpaulosky/dotfiles#180, mpaulosky/dotfiles#182…
Re-Apply the repo-ci-baseline Template so this repo carries the Template changes from mpaulosky/dotfiles#176, mpaulosky/dotfiles#178, mpaulosky/dotfiles#180, mpaulosky/dotfiles#182…
Re-Apply the repo-ci-baseline Template so this repo carries the Template changes from mpaulosky/dotfiles#176, mpaulosky/dotfiles#178, mpaulosky/dotfiles#180, mpaulosky/dotfiles#182…
Requested by Matthew · project thread
Directory.Packages.props: add NU1901, NU1902, NU1903 and NU1904 (low, moderate, high and critical) to WarningsAsErrors. NuGet applies this to restore, so it also covers transitive packages. Only…
Start with the essentials, then dive deeper into collaboration, security, and reference material.
Read the purpose, stack, solution layout, and design principles driving TicketManager.
Open architectureSee contribution expectations, folder structure, and the collaboration flow for future changes.
Open contributing guideReview the security policy, code of conduct, and references published alongside the project.
Open security policy