Maintaining software projects involves more than writing code. It also means welcoming contributions, keeping dependencies up to date, reviewing changes and paying attention to security.
This repository brings together guidance and automation shared across my projects. The goal is to avoid repeating the same work and keep practices consistent, while letting each repository make its own decisions.
- Makes collaboration easier. Provides templates for reporting bugs, suggesting improvements and submitting contributions, alongside support and security guidance.
- Helps keep .NET up to date. Checks SDK versions and can suggest updates through pull requests instead of changing projects' default branches directly.
- Makes projects easier to understand. Collects information about .NET projects and highlights issues in automation tooling.
- Supports code review and security. Offers checks for accidentally exposed credentials and shared code-review configurations.
- Organizes AI agent guidance. Maintains reusable instructions and skills that individual projects can adopt.
- Helps track improvements. Brings quality-related GitHub issues together in a project view.
flowchart TB
Hub[".github shared foundation"] --> Guidance["Guides and templates"]
Hub --> Automation["Automation and checks"]
Hub --> Review["Review, security and agent guidance"]
Guidance --> Repositories["Project repositories"]
Automation --> Reports["Reports and pull requests"]
Reports --> Repositories
Review --> Repositories
Some files provide shared community defaults when a repository doesn't have its own version. Other tasks run through GitHub Actions: they produce reports or propose changes for review.
For example, when an eligible .NET SDK update is available, an automation can open a pull request. The people maintaining that project still decide whether to accept it.
Not every feature is installed automatically. Each repository can keep its own settings and choose the integrations that make sense for it.
The Repo Control Center is a complementary public dashboard for following builds, security, releases, activity and technology versions across my repositories. It collects public information independently rather than controlling the automations here.
- Architecture: how the components fit together, with diagrams.
- Automation catalog: all 13 workflows and their responsibilities.
- Visual workflows: step-by-step diagrams of the main processes.
- Operations: how to run, troubleshoot and safely recover automations.
Suggestions and corrections are welcome. See the contribution guidelines. For potential vulnerabilities, follow the security policy rather than opening a public issue.