{"action":"opened","issue":{"url":"https://api.github.com/repos/BookStackApp/BookStack/issues/777","repository_url":"https://api.github.com/repos/BookStackApp/BookStack","labels_url":"https://api.github.com/repos/BookStackApp/BookStack/issues/777/labels{/name}","comments_url":"https://api.github.com/repos/BookStackApp/BookStack/issues/777/comments","events_url":"https://api.github.com/repos/BookStackApp/BookStack/issues/777/events","html_url":"https://github.com/BookStackApp/BookStack/issues/777","id":310132345,"number":777,"title":"Edit Content and push to Git Repo","user":{"login":"tuaris","id":5660265,"avatar_url":"https://avatars0.githubusercontent.com/u/5660265?v=4","gravatar_id":"","url":"https://api.github.com/users/tuaris","html_url":"https://github.com/tuaris","followers_url":"https://api.github.com/users/tuaris/followers","following_url":"https://api.github.com/users/tuaris/following{/other_user}","gists_url":"https://api.github.com/users/tuaris/gists{/gist_id}","starred_url":"https://api.github.com/users/tuaris/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tuaris/subscriptions","organizations_url":"https://api.github.com/users/tuaris/orgs","repos_url":"https://api.github.com/users/tuaris/repos","events_url":"https://api.github.com/users/tuaris/events{/privacy}","received_events_url":"https://api.github.com/users/tuaris/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-30T18:12:52Z","updated_at":"2018-03-30T18:12:52Z","closed_at":null,"author_association":"NONE","body":"Desired Feature:\r\n\r\nDependent on #776.  This feature describes how Bookstack can be used as an editor for Markdown files stored in a remote Git repository.\r\n\r\n##### Expected Behavior\r\n\r\nAssuming a Book exists or has been created using feature #776 \r\n\r\nThe editor mode should (ideally) be Markdown, but feature #458 could also apply here.  With Markdown Bookstack can define it's own content/file/directory structure on how the files should be organized.  Perhaps something compatible to Read The Docs or Gitbook. \r\n\r\nCreating a new page and saving it will create the file on local storage, perform a `git add .` and then a `git commit` using the current user's email address and name, then finally a `git push`.  Editing an existing document follows a similar process.  Chapters would correspond to sub directories.\r\n\r\nTo handle cases when more than one user edits a page in a given moment.  I think Bookstack already solves this problem with the \"Draft\" feature.  This should prevent conflicts."}}
{"actor":{"display_login":"tuaris"}}