You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2020. It is now read-only.
I know we had backed out of supporting the notion of branches previously, but if I recall correctly, the previous implementation allowed it to replace the commit in the wit-manifest.json.
While I don't know exactly what the full semantics for branches would be, I think it would be helpful to capture in the wit-manifest.json as a supplement to and not a replacement for the commit. It would at least be very helpful for a human reading it to easily see what branch a release is on.
It looks like Git submodules has some concept of branches, so I think we should take a look at that and think about how their conception of branches may or may not translate to Wit.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I know we had backed out of supporting the notion of branches previously, but if I recall correctly, the previous implementation allowed it to replace the commit in the wit-manifest.json.
While I don't know exactly what the full semantics for branches would be, I think it would be helpful to capture in the wit-manifest.json as a supplement to and not a replacement for the commit. It would at least be very helpful for a human reading it to easily see what branch a release is on.
It looks like Git submodules has some concept of branches, so I think we should take a look at that and think about how their conception of branches may or may not translate to Wit.
The text was updated successfully, but these errors were encountered: