Somnibyte/sherpa

Development best practices for Intrepid

Sherpa

Development best practices for Intrepid

Contribution rules:

• Two developers must approve before merging contributions
• One developer veto blocks contribution for review & revision
• Use the github issue functionality if you find something is missing & should be added to Sherpa

Style Guides

• iOS
  • Swift
  • Objective-C
• Android
  • Android OS Project Style Guide
  • Intrepid Style Template
• Ruby
• Elixir
• C#

Process

• Intrepid Development Principles
• Git Workflow
• Pull Request Guidelines
• Why rebase?
• CocoaPods Processes

Maintenance Readme Template

Projects repos should always contain a README so that future development teams can learn about processes/specific quirks that have to do with individual projects. See the template here.

Advice

• Mobile API Guidance

Resources

• iOS Resources
• iOS Build Reporting On Jenkins Via Danger
• iOS Code Coverage On Jenkins
• Android Jenkins setup instructions
• Stuff to read for Android devs
• Stuff to read for iOS devs
• Stuff to read for backend devs
• Intrepid internal resources
• Git cookbook
• Common CocoaPods
• iOS Recommended Tools