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
Hi,
We are using this module extensively in our organizations and have deployed more than 20 landing zones at level3 and level4 and growing at a rapid pace. My question is as we are expanding and deploying application resources we discovered that some of the application level resources have bugs and we often realize about those bugs when we deploy those resources in our environment. We know that those bugs can be easily fixed but that would require some patience at our end however in some cases we can't wait because of some internal requirements. That leads to development of custom modules internally and integrate them in CAF.
As we are expanding we were thinking of forking this repository locally so that we can make those changes in that local repo directly (correct me if I am wrong because I have not worked with forked repos) and also get the updates from parent repo.
Can you please help me in understanding the best practices around forking or is there any alternative way we can solve this issue?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
We are using this module extensively in our organizations and have deployed more than 20 landing zones at level3 and level4 and growing at a rapid pace. My question is as we are expanding and deploying application resources we discovered that some of the application level resources have bugs and we often realize about those bugs when we deploy those resources in our environment. We know that those bugs can be easily fixed but that would require some patience at our end however in some cases we can't wait because of some internal requirements. That leads to development of custom modules internally and integrate them in CAF.
As we are expanding we were thinking of forking this repository locally so that we can make those changes in that local repo directly (correct me if I am wrong because I have not worked with forked repos) and also get the updates from parent repo.
Can you please help me in understanding the best practices around forking or is there any alternative way we can solve this issue?
Beta Was this translation helpful? Give feedback.
All reactions