BrunoGaoandBrunoGaoSZ
e29e2eed81
* fix(ci): sanitize branch docker tags for ghcr builds * feat(governance): finalize lifecycle controls and compliance baseline * fix(governance): unblock p0 policy and gate checks * fix(governance): add drift soft-fail and compile compatibility layer * fix(app): scan legacy mapper package for mybatis * fix(coverage): add jacoco and bootstrap soft-fail gate * fix(gate): stabilize spec-quality and analysis lint checks * fix(governance): restore legacy app imports for coverage build * fix(ci): include master branch in ci triggers * fix(ci): stabilize backend and frontend required checks * fix(ci): allow frontend install without frozen lockfile * fix(ci): soft-fail frontend lint in required check --------- Co-authored-by: BrunoGaoSZ <[email protected]>
824 B
824 B
Code of Conduct
Our Standards
We are committed to a collaborative and professional engineering environment. Participants are expected to:
- be respectful and constructive in technical discussions
- provide actionable, evidence-based feedback
- assume good intent and focus on problem-solving
- keep discussions on-topic and repository-traceable
Unacceptable behavior includes harassment, personal attacks, discrimination, intimidation, deliberate disruption, or sharing private information without permission.
Reporting
Report conduct issues to repository maintainers via private channel.
For security-sensitive incidents, use the process in SECURITY.md.
Enforcement
Maintainers may remove comments, close discussions, or restrict repository permissions for behavior that violates this Code of Conduct.