Zeppelin-540: Notebook versioning control, commit from frontend notebook menu#577
Zeppelin-540: Notebook versioning control, commit from frontend notebook menu#577khalidhuseynov wants to merge 21 commits into
Conversation
|
@khalidhuseynov Thanks for the contribution. I think the approach make sense, but the implementation need to be more generalized. We must not assume that user will use git notebook repo. How about add one more interface to NotebookRepo? and let all notebookrepo implement this interface. This method can be invoked with proposed GUI. What do you think? |
|
@Leemoonsoo yes that makes it more flexible and makes sense, I'll address it soon. |
|
guys you have some communication channel, I enjoyed the project and want to help |
There was a problem hiding this comment.
How about just setMessage(commitMessage) as a commit message? is there special reason adding "Updated " + pattern in front?
There was a problem hiding this comment.
good point! Actually as I've checked now, pattern from setMessage isn't used anywhere else. addressed it in b0fa219
|
@maaark11 Thanks for the interest : ) |
Conflicts: zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/repo/NotebookRepoSync.java
31906bd to
339c9fe
Compare
99c7122 to
b0fa219
Compare
|
tests were added, ready for review |
There was a problem hiding this comment.
Can we use just 'message' or 'commitMessage' instead of 'gitCommitMessage' for the field name?
|
@Leemoonsoo yes exactly! I was going to change git related things, but also wanted to hear community on |
Conflicts: zeppelin-server/src/main/java/org/apache/zeppelin/socket/Message.java zeppelin-server/src/main/java/org/apache/zeppelin/socket/NotebookServer.java
Conflicts: zeppelin-zengine/src/test/java/org/apache/zeppelin/notebook/repo/NotebookRepoSyncTest.java
b5345df to
64111e0
Compare
| } | ||
| git = new Git(localRepo); | ||
| maybeAddAndCommit("."); | ||
| checkpoint(".", "initialization commit"); |
There was a problem hiding this comment.
I think this shouldn't be executed when Git repo already exists. Isn't it?
There was a problem hiding this comment.
right, that's more friendly. Actually I changed it not to commit even at first start when initializing Git repo. So on first start all the notebooks will be unstaged, and user will explicitly commit whenever needed.
3312ece to
3f510d1
Compare
3f510d1 to
4f04af0
Compare
|
Thanks for addressing comment. |
|
Merge if there're no more discussions |
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
checkpointinterfaceerror propagation to front-endin a separate PRIs there a relevant Jira issue?
ZEPPELIN-540
How should this be tested?
GitNotebookRepoas a storage in/conf/zeppelin-site.xmlgitmenu to commitgit login/notebooksfolderScreenshots (if appropriate)
Questions: