-
Notifications
You must be signed in to change notification settings - Fork 6
do not assume default ref to be master #617
Comments
would be interesting to see what breaks if no ref is present :-) but I assume it is most of the times read from the strains, so should be present. a problem will be, if a customer uses a different default branch than helix-pages.... |
this should allow us to support main and master, assuming helix-resolve-git-ref is used consistently downstream fixes #617
adobe/helix-pages#491 is the more effective change |
I do not think the proposed change in adobe/helix-pages#491 is what we need / is enough, especially after my last changes adobe/helix-pages@70b582a. There are 4 cases to cover at 2 different places:
Assuming that " This requires to also rework this block: helix-publish/layouts/fastly/helix.vcl Lines 266 to 272 in 172a1be
|
which in the end should be simple: logically replace I can look at it next week. |
helix-publish/layouts/fastly/helix.vcl
Line 271 in 172a1be
We may be able to just keep it empty since adobe/helix-resolve-git-ref#253 added a default branch fallback
The text was updated successfully, but these errors were encountered: