Clarify branching model?

[deliciouslytyped]

Is it explicitly stated anywhere whether branching off branches works? It seems to, but I don't see the parent branch mentioned anywhere in the UI, so without experimenting, its not clear what the branching model (and target featureset) of this plugin is exactly.

The documentation seems to beat around the bush a bit, but doesn't expound on what, if any (and there certainly are) limitations there are. As someone coming from git my expectations were unrealistically high.

Edit: I was looking at https://docs.netboxlabs.com/netbox-extensions/branching/ , which maybe out of date. It's not clear what version this is.

[deliciouslytyped]

For example, can you branch off a branch or are all branches off main only?
https://docs.netboxlabs.com/netbox-extensions/branching/#terminology seems to suggest branches are only off of, and merge back into main. The REST API also doesn't seem to expose anything for specifying which branch to branch off of.

On the other hand, when branching in the web UI, it seems that implicitly you can branch off of an activated branch?

[deliciouslytyped]

Oh actually I guess the way you would replicate that with REST would be to set the header for choosing an active branch and then do the branching.

Nevertheless, the web ui doesnt seem to show the source branch of a branch, even though this seems to work? Is this intended behavior or emergent behavior of the database schema based branching?