Zarf Big Bang extension doesn't support branches

[runyontr]

When moving repos, zarf can't support moving a branch over in the same way that it supports pinning to a tag or a git commit.

[dgershman]

When moving repos, zarf can't support moving a branch over in the same way that it supports pinning to a tag or a git commit.

Have you been able to get commits to work? I haven't been able to.

[dgershman]

When moving repos, zarf can't support moving a branch over in the same way that it supports pinning to a tag or a git commit.

Have you been able to get commits to work? I haven't been able to.

Nevermind, this is a limitation of the bigbang extension.

[dgershman]

When moving repos, zarf can't support moving a branch over in the same way that it supports pinning to a tag or a git commit.

Have you been able to get commits to work? I haven't been able to.

Nevermind, this is a limitation of the bigbang extension.

Actually it looks like a limitation of pulling Charts, it's restricted to tags.

[dgershman]

I was able to work around this by setting the version as refs/heads/<branchname>

[dgershman]

Eventually this falls when flux source-controller gets confused about the reference.

couldn't find remote ref \"refs/tags/refs/heads/master\

[Racer159]

@dgershman the issue you were seeing was fixed in #1613 correct?

(also git branch support was added in https://github.com/defenseunicorns/zarf/releases/tag/v0.25.0)

[dgershman]

#1613 did not fix the issue. I worked around no branch support by forking BB from Github and then using repo and a tag I cut myself. Branches do not seem to work for me.

[dgershman]

This was in preparation for the `2.0.0` tag coming soon on BB. Here is my draft PR #1611.

[Racer159]

Renaming to Zarf Big Bang extension doesn't support branches since Zarf itself does