GitHub user khalidhuseynov opened a pull request: https://github.com/apache/incubator-zeppelin/pull/577
Zeppelin-540: Notebook versioning control (git commit) from frontend notebook menu ### What is this PR for? This PR improves the front-end experience to use git versioning on notebooks. Any community feedback is welcome. ### What type of PR is it? Improvement ### Todos * [x] - front-end and back-end changes * [ ] - error propagation to front-end * [ ] - tests ### Is there a relevant Jira issue? [ZEPPELIN-540](https://issues.apache.org/jira/browse/ZEPPELIN-540) ### How should this be tested? 1. Uncomment `GitNotebookRepo` as a storage in `/conf/zeppelin-site.xml` 2. Start Zeppelin 3. Make changes to some notebook 4. Use `git` menu to commit 5. To check whether successfully committed, do `git log` in `/notebooks` folder ### Screenshots (if appropriate)  ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No You can merge this pull request into a Git repository by running: $ git pull https://github.com/khalidhuseynov/incubator-zeppelin feat/git-commit-frontend-access Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-zeppelin/pull/577.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #577 ---- commit 2ebe628bd19748bcd1535e9b22f0918d79d7e7d4 Author: Khalid Huseynov <khalid...@nflabs.com> Date: 2015-12-29T02:32:42Z add button and git menu commit 8069ccd678f2d37b9280b95e83982a061fceadc4 Author: Khalid Huseynov <khalid...@nflabs.com> Date: 2015-12-29T02:36:32Z add frontend handler via websocket commit a1894c26b934f92292ade851865ce89200efacff Author: Khalid Huseynov <khalid...@nflabs.com> Date: 2015-12-29T02:37:33Z backend handling of git notebook commit ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---