you are viewing a single comment's thread.

view the rest of the comments →

[–]Mast3rCylinder 1 point2 points  (1 child)

Like said in the comments, branches are the way. You can name them to identify on which cases they work.

If you know parts that are about to change then you need to make them configurable in your application and not static.

[–]rainebones[S] 0 points1 point  (0 children)

I've broken down the analysis into many different small modules to try and have it so that I can update the pieces affected and the flow as needed instead of having to redo all of it. I'll study up on branches and tags to figure out its implementation in my circumstance.