-
Notifications
You must be signed in to change notification settings - Fork 26
Coding Standards
Tiffany edited this page Mar 29, 2023
·
1 revision
When naming your branch, start with indicating who wrote it. Most developers will use the first letter of their first name and their last name (e.g. Another Developer becomes adeveloper). If your last name is long or complicated you can abbreviate to your initials. Then indicate the ticket number the branch is for. Lastly, add a short kebab case description of the ticket.
adeveloper/101-coding-standards
When naming a PR, start with the ticket number, so that it's easier to find, then add the full ticket name
101 Specifying naming standards for creating PRs
- Team Working Agreement
- Team composition
- Workflows and processes
- Testing and bug filing
- Accessing eAPD
- Active Documentation:
- Sandbox Environment
- Glossary of acronyms
- APDs 101
- Design iterations archive
- MMIS Budget calculations
- HITECH Budget calculations
- Beyond the APD: From Paper to Pixels
- UX principles
- User research process
- Visual styling
- Content guide
- User research findings
- eAPD pilot findings
- User needs
- Developer info
- Development environment
- Coding Standards
- Development deployment
- Infrastructure Architecture
- Code Architecture
- Tech 101
- Authentication
- APD Auto Saving Process
- Resetting an Environment
- Hardware Software List
- Deploying Staging Production Instances Using Scripts
- Terraform 101 for eAPD
- Provisioning Infrastructure with Terraform
- WebSocket basics
- Operations-and-Support-Index
- Single Branch Deployment Strategy
- Ops and Support Overview
- Service Level AOI
- Incident Response Plan
- On-Call Policy
- Infrastructure Contingency Plan
- Updating CloudFront Security Headers
- Requesting and Installing TLS Certificates