Dear Databricks,
We have noticed the following issue since the new default notebook format has been set to IPYNB. When we release our code from (for example) DEV to TST using a release pipeline built in Azure DevOps, we see unintended changes popping up on the ACTIVE branch on there.
These changes are not in the code itself, but rather in the new metadata details that come with the new IPYNB files. In this screenshot, you see changes in the 'cellMetadata' section. But we also see changes to the following sections, for example: 'client', 'environment_version', and 'inputWidgetPreferences'.
When we then do a follow-up release that also touches one of those notebooks, we get an error doing the release process because there is an outstanding change in the notebook already on the ACTIVE branch.
What makes this issue even more sticky, is that we cannot discard the changes via the Git menu. We cannot discard the change individually. And we cannot discard all changes simultaneously. (Or maybe they - are - in fact discarded but then the change goes back into effect immediately?)
Any help would be much appreciated!
