Skip to main content

Getting Started

Welcome to the Rizing developer guide. The purpose of this section is to provide a comprehensive view of development practices at Rizing.

🏁 Starting Point​

To get started working within Rizing's development workflows, we suggest you first understand the core development concepts and technology stacks used within the company.

The following steps will help in getting you started:

  1. Review Branching Model - review and understand Rizing's branching workflow.
  2. Review Development Workflow - review and understand Rizing's development workflow.
  3. Review Coding Standards - review and understand Rizing's coding standards.
  4. Learn Azure Devops - learn Rizing's Version Control System and ticketing platform Azure DevOps.
  5. Explore Projects - navigate and explore available Rizing projects at https://dev.azure.com/rizing-devops.
    1. Recommended: https://dev.azure.com/rizing-devops/rizing/_git/monorepo (docs are maintained here)
    2. More info on this monorepository can be found here

☁️ Azure DevOps​

Azure DevOps provides development and project management tooling and is used within Rizing. Azure DevOps provides the following capabilities:

  • Azure Boards: Deliver value to your users faster using proven agile tools to plan, track, and discuss work across your teams.
  • Azure Pipelines: Build, test, and deploy with CI/CD that works with any language, platform, and cloud. Connect to GitHub or any other Git provider and deploy continuously.
  • Azure Repos: Get unlimited, cloud-hosted private Git repos and collaborate to build better code with pull requests and advanced file management.
  • Azure Test Plans: Test and ship with confidence using manual and exploratory testing tools.
  • Azure Artifacts: Create, host, and share packages with your team, and add artifacts to your CI/CD pipelines with a single click.
  • Extensions: Access extensions from Slack to SonarCloud to 1,000 other apps and servicesβ€”built by the community.
tip

If you are a new hire, you may need to request access to Rizing's Azure DevOps site at https://dev.azure.com/rizing-devops.

🌈 Summary​

  • Source Control: Use Git with conventional commits
    • ex: fix(server): send cors headers
  • Versioning: Use Semantic Versioning
  • Branching Model: Release branch model (main, release/*, [product]/[user]/*)
    • Release branch ex: release/omni/v1.0.0
    • Feature branch ex: omni/russell.green/1234-my-feature
  • Goals: automated, consistent, and repeatable processes