-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set repo as template repository #94
Comments
Just providing my 2c as well. My company needs a solution like this as well. I have a runway of ~10 projects that will use DABs / MLOps stacks. I maintain a custom MLOps stack implementation in Azure DevOps where my projects live in a monorepo. When this repo gets an update, here are my steps to update my projects:
I concur that it would be nice to have the ability to easily maintain a custom stack that syncs with this repo AND update existing projects. |
Hi @followingell @jackroseman thanks for the feedback! We are looking into options that would allow us to maintain the current customizability of MLOps Stacks but also propagate changes to downstream generated Stacks. With a Github Template Repository, it becomes difficult to initialize the project with custom variables to the extent that we have it. For now, for forks we recommend pulling in the latest changes, and for already initialized projects, you can generate a project using the latest version of MLOps Stacks with the same parameters, add the code as a branch to your existing repo, and create a PR/perform a diff to see which of the latest changes you'd like to keep and which don't suit your purposes. |
@arpitjasa-db Thanks for the response and pointers. Just sharing this blogpost which may help guide you in finding a solution 🙂 👍 |
Hello Databricks,
Given the below:
Would it be possible/more-appropriate to set this repository as a template repository?
This would mean that users could easily create private "custom stacks" (e.g. for organizations) as per your Stack Customization Guide without the need to do a complex private fork procedures.
I look forward to hearing back!
The text was updated successfully, but these errors were encountered: