GitHub user tinkoff-dwh reopened a pull request:

    [ZEPPELIN-2813] revisions comparator

    ### What is this PR for?
    Sometimes need to see the difference between versions and to switch to 
another version and look for changes are not convenient (the page reloaded). 
This feature allows you to compare any two versions of the notebook.
    ### What type of PR is it?
    ### What is the Jira issue?
    ### How should this be tested?
    1 make some commits. Сchange the contents of paragraphs (delete, add, edit)
    2 open Revisions comparator
    3 compare revisions and check diff
    ### Screenshots (if appropriate)
    ### Questions:
    * Does the licenses files need update? yes (updated)
    * 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 ZEPPELIN-2813

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2506
commit a192b95dbb1f8b1cb07123194c77a12c28978eec
Author: Tinkoff DWH <>
Date:   2017-07-27T12:31:07Z

    [ZEPPELIN-2813] revisions comparator for note

commit b9498142b40d80ba07581818011996a66056a9f3
Author: Tinkoff DWH <>
Date:   2017-07-27T14:35:26Z

    [ZEPPELIN-2813] license

commit 4ce5286c80a5ed022aa7d171f8e1614158d73f1b
Author: tinkoff-dwh <>
Date:   2017-08-01T04:28:27Z

    Merge remote-tracking branch 'origin/master' into ZEPPELIN-2813

commit 514b3f57bce2acfe94965142c9a8d8f357ce2f3f
Author: tinkoff-dwh <>
Date:   2017-08-01T05:42:52Z

    small fixes, added documentation

commit dc67f8fad302b93fbc3de297226695be4e14f294
Author: tinkoff-dwh <>
Date:   2017-08-09T09:43:50Z

    [ZEPPELIN-2813] refactoring


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 or file a JIRA ticket
with INFRA.

Reply via email to