SoloDevBoard

A single pane of glass for solo developers managing GitHub workloads across multiple repositories.

IMPORTANT SoloDevBoard is currently in early development. The project is under active development (or as active as my schedule will allow at least!). Please refer to the project plan for the current roadmap and feature status.

What Is SoloDevBoard?

SoloDevBoard is a .NET 10 Blazor Server application that consolidates your GitHub repository management into a single, unified interface. If you maintain multiple GitHub repositories as a solo developer, SoloDevBoard eliminates the context-switching between repository tabs, project boards, settings pages, and workflow runs.

Feature	Description	Status
Audit Dashboard	Consolidated view of issues, open PRs, label consistency, and workflow health across all repositories.	Available
Label Manager	Create, edit, synchronise, and enforce label taxonomies across multiple repositories from a single interface.	Available
Repositories	View and manage repositories accessible to your GitHub account.	Available
One-Click Migration	Migrate labels and milestones from one repository to another in a single action. Project board migration is planned.	Partially Available
Board Rules Visualiser	Visualise supported board states and transitions for GitHub Project v2 boards.	Partially Available
Triage UI	Keyboard-friendly interface for triaging incoming issues quickly.	Available
Workflow Templates	Browse, customise, and apply GitHub Actions workflow templates across repositories.	Coming Soon

Tech Stack

• .NET SDK 10.0 or later.
• Git (any recent version).
• A GitHub account.
• A GitHub Personal Access Token (PAT) or GitHub App for API authentication.

Getting Started

Prerequisites

Ensure you have the following installed:

• .NET SDK 10.0 or later.
• Git.
• A GitHub account.
• A GitHub Personal Access Token (PAT) or GitHub App for API authentication.
• The Aspire CLI (aspire) for local orchestration.

Run Locally

SoloDevBoard uses Aspire for local orchestration and production deployment to Azure Container Apps. Two authentication modes are available: PAT mode (default, for solo local development) and hosted sign-in (GitHub App, for production). See Getting Started for the full mode guide.

Quick start with Aspire (recommended):

# Clone the repository
git clone https://github.com/markheydon/solo-dev-board.git
cd solo-dev-board

# Restore dependencies
dotnet restore SoloDevBoard.slnx

# Configure GitHub auth — one secret for PAT mode
aspire secret set Parameters:gh-pat "<your-pat>"

# Start with Aspire
aspire start --apphost src/SoloDevBoard.AppHost/SoloDevBoard.AppHost.csproj

# Get the allocated endpoint
aspire describe

Open the app resource URL shown by aspire describe in your browser.

Optional legacy path (without Aspire):

dotnet user-secrets set "GitHubAuth:PersonalAccessToken" "<your-pat>" --project src/App/SoloDevBoard.App
dotnet run --project src/App/SoloDevBoard.App

For hosted sign-in mode (GitHub App), see docs/getting-started.md or src/SoloDevBoard.AppHost/README.md.

Aspire is used for both local orchestration and production deployment to Azure Container Apps. See docs/deployment.md for Azure deployment instructions.

Project Structure

solo-dev-board/
├── src/SoloDevBoard.AppHost/     # Aspire AppHost (local orchestration and Azure deployment)
├── src/SoloDevBoard.ServiceDefaults/  # Aspire service defaults (telemetry, health checks)
├── src/
│   ├── App/                    # Blazor Server UI (presentation layer)
│   ├── Application/            # Use cases and service interfaces
│   ├── Domain/                 # Domain entities and value objects
│   └── Infrastructure/         # GitHub API clients, external integrations
├── tests/
│   └── App.Tests/              # xUnit test projects
├── docs/
│   ├── index.md                # Project overview (GitHub Pages)
│   ├── getting-started.md      # Setup and configuration guide
│   ├── deployment.md           # Azure Container Apps deployment guide
│   └── user-guide/             # Per-feature user guides
├── plan/
│   ├── SCOPE.md                # Project scope and constraints
│   ├── IMPLEMENTATION_PLAN.md  # Phased development plan
│   ├── BACKLOG.md              # Feature backlog by epic
│   ├── RELEASE_PLAN.md         # Versioning and release process
│   ├── LABEL_STRATEGY.md       # GitHub label taxonomy
│   ├── PROJECT_MANAGEMENT.md   # Issues, milestones, and project board guide
│   ├── PROJECT_BOARD_DESIGN.md # Project board column and automation design
│   └── DOCS_STRATEGY.md        # Documentation conventions
├── adr/
│   ├── README.md               # ADR index
│   ├── 0001-blazor-server.md
│   ├── 0002-testing-framework.md
│   ├── 0003-bicep-infrastructure.md
│   ├── 0004-layered-architecture.md
│   └── 0005-github-api-strategy.md
├── .github/
│   ├── copilot-instructions.md  # GitHub Copilot custom instructions
│   ├── agents/                  # Copilot agent definitions
│   ├── prompts/                 # Copilot workflow prompts
│   ├── ISSUE_TEMPLATE/          # Issue templates (feature, bug, chore)
│   ├── pull_request_template.md
│   └── workflows/
│       ├── ci.yml               # CI: build and test on every PR
│       ├── cd.yml               # CD: Aspire deploy to Azure (manual until first success)
│       └── aspire-deploy-validate.yml  # Validates AppHost deployment model on PR
├── .agents/
│   └── skills/                  # Shared skills (Copilot + Cursor)
├── .cursor/
│   ├── rules/                   # Cursor path-scoped rules
│   └── commands/                # Cursor slash commands (/implement-issue, etc.)
└── AGENTS.md                    # Platform-neutral AI collaborator standards

---

Contributing

SoloDevBoard welcomes contributions from all developers.

To contribute:

1. Fork the repository and create a new branch for your changes.
2. Review the project structure and existing documentation to understand the architecture and conventions.
3. Ensure all code comments, string literals, and documentation use UK English spelling.
4. Follow the coding conventions outlined in .github/copilot-instructions.md.
5. Use the issue templates in .github/ISSUE_TEMPLATE/ to report bugs or request features.
6. When implementing a feature or fix, reference the relevant issue in your commit message.
7. Add or update tests in the appropriate test project under tests/.
8. Submit your changes via a pull request using the provided template.
9. The CI workflow will build and test your changes automatically.
10. The project maintainer will review your PR and provide feedback or merge when ready.

For guidance on labels, see plan/LABEL_STRATEGY.md. For help with setup, see docs/getting-started.md.

---

AI-Driven Development

SoloDevBoard is developed by a solo developer with GitHub Copilot as an active AI collaborator. The .github/copilot-instructions.md file contains custom instructions that guide Copilot on architecture, conventions, UK English requirements, and documentation responsibilities. When using Copilot Chat to add features or make changes, these instructions ensure consistent, well-structured output.

---

Licence

SoloDevBoard is released under the MIT Licence.