Create coding standards and style guide - #463
Merged
Merged
Conversation
… standards - shortheartone#407 BUG_TRIAGE.md: weekly triage cadence, S1-S4 severity, P1-P4 priority, SLA table (S1=24h, S2=1wk, S3=4wk), triage checklist, label reference, bug lifecycle, triage report template, escalation path. Updated .github/ISSUE_TEMPLATE/bug_report.md with severity self-assessment and maintainer triage checklist. - shortheartone#408 SECURITY.md: rewritten with dual reporting channels (email + GitHub Advisory), response timeline (48h ack, 14d S1 fix), embargo policy per severity, vulnerability handling workflow, in/out-of-scope lists, credit and Hall of Fame, bug bounty statement, full advisory template. - shortheartone#409 CHANGELOG.md: added contributor guide, versioning guide (MAJOR/MINOR/ PATCH rules with Soroban contract deployment note), and release notes template with Breaking Changes section and upgrade checklist. All existing entries preserved. - shortheartone#410 CODING_STANDARDS.md: Rust and React/TypeScript standards covering naming, structure, doc comments, error handling, security-critical patterns (require_auth-first, CEI), performance conventions, and testing. Added rustfmt.toml, .clippy.toml, frontend/eslint.config.js (flat config). Updated frontend/package.json (fixed duplicate test key, added lint:fix). Updated .githooks/pre-commit to also run frontend lint and typecheck.
…-408-409-410 docs: add bug triage, security policy, changelog template, and coding standards (shortheartone#407–shortheartone#410)
|
@oncleweynom Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Provide a short summary of the changes in this pull request.
Changes
List the main changes made in this PR (code, docs, configuration).
Testing
Describe how the changes were tested. Include commands, test suites, or manual steps.
Breaking Changes
Note any changes that may break existing behavior or require migrations.
Documentation
CHANGELOG.mdupdated under[Unreleased]docs/API.mdupdated if contract API changedREADME.mdupdated if usage or setup changed///)Checklist
CHANGELOG.md(if applicable)closes #407
closes #408
closes #409
closes #410