Repository navigation
Code Quality Gates
The automated bars every change must clear before it merges. These run in CI (CI/CD Pipeline) and, for Sonar, locally before push.
In CI, Sonar runs as the _sonar stage inside the single-run ci.yaml pipeline (it skips Dependabot PRs); a full type-aware analysis runs nightly via sonar-cloud-analysis.yml - see CI/CD Pipeline.
Four separate projects, one per app:
yosemitecrew_Yosemite-Crew_Backendyosemitecrew_Yosemite-Crew_Frontendyosemitecrew_Yosemite-Crew_MobileAppYCyosemitecrew_Yosemite-Crew_Desktop
Quality-gate, coverage, bugs, code-smell, and reliability badges are on the README. Representative rules for new code:
| Rule | Requirement |
|---|---|
| Cognitive complexity | ≤ 15 per function |
| Duplicated lines | ≤ 3% |
| New-code coverage | ≥ 80% (frontend targets higher — see Testing Strategy) |
| New code smells | Zero |
| New bugs | Zero |
| Security hotspots | All reviewed |
| Reliability / Security rating | A |
Common patterns: no nested ternaries, no unused vars/imports, no any, no console.log in production code (use the logger), extract magic numbers into named constants. The full enforced rule set lives in the per-app Sonar guidance in the repo.
Sonar findings are fixed locally before pushing — never let issues or security hotspots first surface on the PR. Review every reported issue and hotspot (not just gate-failing ones) and re-run until clean before opening the PR.
PR/CI notes: the local scan analyzes your branch/
main, not the PR itself — read the PR gate via the SonarCloud API. New-code coverage on a PR can be inflated by a stale baseline (pre-existing files counted as "new"); to hit a target you may need to cover those too. A CONFLICTING/DIRTY PR silently skipspull_requestActions — resolve conflicts first.
React changes run through react-doctor - lint, accessibility, bundle-size, and architecture diagnostics. In CI, react-doctor.yml runs on every PR and posts a sticky summary comment; repo-level exclusions live in react-doctor.config.json. Run it locally after finishing a feature / before committing React code - it fetches the canonical triage playbook and includes a regression check.
Code is scanned against Aikido (SAST + exposed-secret detection) before pushing or opening a PR — a standing rule alongside the Sonar gate. See Security.
pre-commit scans staged changes with Secretlint and the repo staged-secret scanner; if gitleaks is installed locally it also runs gitleaks protect --staged --redact. GitHub Actions scans again with Gitleaks. Never commit .env files, tokens, or keys; a suspected leak means rotate immediately, then follow SECURITY.md.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki