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
The 'link => true' feature from bkuebler in #6 for syncing 'linked' environments is very cool and useful if you are working in predefined environments (dev->prelive->live).
But with this feature you are currently forced to create 'own' branches for every linked module to have a working puppet-environment (working g10k-sync).
So it is not easy to create own branches anymore for testing.
For that a kind of 'link-fallback' would be great.
So that g10k still tries to sync a branch with the same name as the environments branch, but if this does not exist using the fallback-branch.
That fallback-branch could for example be set 'hard-coded' to the default-branch of the git - or could be configured by an additional 'link-fallback'-attribute in Puppetfile.
Thx and Greets
Simon
The text was updated successfully, but these errors were encountered:
The 'link => true' feature from bkuebler in #6 for syncing 'linked' environments is very cool and useful if you are working in predefined environments (dev->prelive->live).
But with this feature you are currently forced to create 'own' branches for every linked module to have a working puppet-environment (working g10k-sync).
So it is not easy to create own branches anymore for testing.
For that a kind of 'link-fallback' would be great.
So that g10k still tries to sync a branch with the same name as the environments branch, but if this does not exist using the fallback-branch.
That fallback-branch could for example be set 'hard-coded' to the default-branch of the git - or could be configured by an additional 'link-fallback'-attribute in Puppetfile.
Thx and Greets
Simon
The text was updated successfully, but these errors were encountered: