I am facing the same issue as Prasad329.
The recommended best practice is "*Always make changes in the GitHub-managed YAML (bundle)*". In my opinion this only makes sense if a good editor is provided for the source artifacts.

For python there are good editors. Both Databricks console and other tools have good editrs.

For dashboards the Databricks console is the only practical editor. Luckily, it is possible to navigate to the *.lvdash.json files in a git-linked bundle folder in the workspace and open the dashboard editor, where changes are then saved back to the git-linked folder and can be committed and pushed etc..

For jobs there is a gap. There seems to be no supported way to directly save the job yaml to a git-linked bundle and no way to open a git-linked yaml into the job editor. At the moment I doing this by cutting and pasting the yaml from file to editor using "edit as yaml" , testing and modifying and pasting back to the file.

I hope the gap is temporary and not "by design". We surely cannot expect that editing yaml in a pure text editor is a better experience than using the special Jobs editor.