Leanblueprint and branches

Stream: general

[Martin Dvořák]

If I have several Git branches in a leanblueprint-driven project, can I preserve the dependency graph for each of them?

[Patrick Massot]

There are two completely different questions. Leanblueprint itself doesn’t care about git branches (or anything git related). But the usual setup where the output is hosted by github.io probably doesn’t allow what you want. So you need to move to a more custom hosting setup.

[Martin Dvořák]

Thanks a lot for clarification of my question and your answer!

[Floris van Doorn]

This should be possible by tinkering with the Github Actions workflow files. Use the ordinary one that triggers when pushing to branch A and a slightly modified one (where you move the dependency graph to a different file name) when pushing to branch B.
(I wouldn't be able to say how to precisely achieve that.)

[Martin Dvořák]

I don't need anything automatic or fancy. I just want to preserve the blueprint and the dependency graph for a release version, to not be affected by future changes on the main branch. It can be a static copy.