3 docs tagged with "best practice"

Release management is a much broader topic than just adopting a tool and if you want to go deeper here is a good starting point to additional resources.

Whether the project is developed by a team or you are the sole contributor you soon need to define your workflow. In version control, this means you have rules and semantics in place to track your code changes consistently. Even when you have never thought about a branching model you're actually using one. This set of rules is often called in many different ways, like branching strategy, branching pattern, git worlflow. A few well known ones are:

Nowadays all teams use CI/CD platforms to automate the build and release process around their software projects but often times they get into some pitfalls like: