We use Databricks widgets in our python notebooks to pass parameters in jobs but also for when we are running the notebooks manually (outside of a job context) for various reasons. We're a small team, but I've noticed that when I create a notebook and add widgets to it (using the notebook UI but clicking on the Edit menu and selecting Add widget...), those widgets don't seem to save to our git repo for other data engineers or scientists when they pull the notebook from Git. So they have to spend time manually adding the widgets back to the notebook, since the notebook assumes they are there and pulls values for them using `dbutils.widgets.get("<widget-name">)`.
Is there a setting or something somewhere that I need to turn on so that the widgets persist with the notebook and will automatically be there at the top of the notebook when someone pulls the notebook from git (obviously assuming the open the notebook in the databricks UI and not on their local desktop)? If not, is there another way I should be handling this scenario? Parameterizing our notebooks is necessary as we often reuse them to populate new instances of a catalog/schema or recreate a table, etc. and setting up a job seems like overkill. How do others handle parameterized notebooks that are stored in git and can be open and run by other team members?
