Last update: 2024-11-18

This page summarizes the most important aspects of how we like to work at Renuo when writing new software. We like to call this “The Renuo Flow”.

The Renuo Flow

The Renuo Flow consists of rules and conventions for Rapid Development.

We will also describe tools and processes to clarify how we define “done” and work with our clients.

We initially took inspiration from Git flow but adapted and simplified it to our needs over time.

Untitled

Our base branch is called develop, and we work on “feature/” branches. There can always be more branches for each feature, depending on the feature's complexity.

<aside> 👉 We like to keep our feature branches as small as possible. In the case of complex features, it is desired and expected that developers work on multiple feature branches.

</aside>

Continuous Integration / Continuous Deployment

Both main and develop branches are connected to an environment via CI/CD.

This guarantees the developers that the latest version of the code in each branch is also the version of the code running on each environment.

<aside> 🔥 We are currently working on allowing Review Apps.

</aside>

Untitled

Our primary and beloved tool for CI/CD is SemaphoreCI.