Jean-Luc Makiola
fbb14f9334
Codeberg became canonical for issues, PRs and releases, but there was nothing telling a contributor how any of it works — no CONTRIBUTING.md at all, and no contributor entry point in the README. The workflow it documents is issue-first: a feature needs a yes-or-no before it needs code, since whether Calendula should do a thing is the one decision a patch cannot make. Both features and bugs get a milestone, and that milestone names the branch a PR targets (2.18.0 -> release/v2.18.0), because main is a release trigger rather than a staging area. Typo and docs fixes skip straight to a PR — an issue-per-typo helps nobody. Two traps get their own sections because both waste a contributor's whole afternoon: translations never go through PRs (Weblate owns every values-* file, German included, and overwrites hand-edits on the next sync), and a clone without --recurse-submodules cannot configure at all, since floret-kit is a composite build compiled from source. The rules section is the invariants that actually turn into review comments — no network, no second database, no hand-patching UI state after a write, domain/ free of Android imports, JVM-first tests, and the reproducible-build flags that the official F-Droid repo depends on.
20 lines
292 B
Markdown
20 lines
292 B
Markdown
---
|
|
name: Question
|
|
about: Ask how something works or get help using Calendula
|
|
title: ""
|
|
labels:
|
|
- question
|
|
---
|
|
|
|
### Your question
|
|
|
|
|
|
### What you've tried
|
|
<!-- so far, if anything -->
|
|
|
|
|
|
### Context
|
|
- Calendula version: <!-- Settings → bottom of the screen -->
|
|
- Android version:
|
|
- Device:
|