Contribute
All Schuly code is on GitHub. Issues labeled bug or feature are a good place to start.
Choose a project
| Project | Stack | Start here |
|---|---|---|
| Mobile app | Flutter | Development setup |
| Server and web app | ASP.NET Core, Angular | Development setup |
| Plugins | .NET | Development setup |
| Plugin contract | .NET, NuGet | Development setup |
| Website | Angular | Development setup |
| Microsoft 365 service | Python, FastAPI | Development setup |
| These docs | VitePress | Editing these docs |
Make a change
Every repository uses the same workflow:
- Open a labeled issue.
- Create a branch from
main, namedfeature/<issue#>_PascalCaseorfix/<issue#>_PascalCase. - Commit with a short, imperative subject, such as
Add agenda filter. - Open a labeled pull request. Its body is a summary and
Closes #<issue>, with no test plan. - Squash-merge the pull request and delete the branch.
Don't commit directly to main, and don't add AI attribution to commits, pull requests, or issues.
Each project's Contributing page lists its own rules.
Labels
| Label | Use for |
|---|---|
bug | Something that's broken |
enhancement | An improvement to existing behavior |
feature | New functionality |
refactor | Internal changes with no change in behavior |
CI/CD | Build, release, and workflow changes |
dependencies | Dependency updates |
documentation | Docs-only changes |
