{"action":"opened","issue":{"url":"https://api.github.com/repos/deni-zen/csvelte/issues/58","repository_url":"https://api.github.com/repos/deni-zen/csvelte","labels_url":"https://api.github.com/repos/deni-zen/csvelte/issues/58/labels{/name}","comments_url":"https://api.github.com/repos/deni-zen/csvelte/issues/58/comments","events_url":"https://api.github.com/repos/deni-zen/csvelte/issues/58/events","html_url":"https://github.com/deni-zen/csvelte/issues/58","id":168805496,"number":58,"title":"Write git policy document","user":{"login":"deni-zen","id":17840996,"avatar_url":"https://avatars.githubusercontent.com/u/17840996?v=3","gravatar_id":"","url":"https://api.github.com/users/deni-zen","html_url":"https://github.com/deni-zen","followers_url":"https://api.github.com/users/deni-zen/followers","following_url":"https://api.github.com/users/deni-zen/following{/other_user}","gists_url":"https://api.github.com/users/deni-zen/gists{/gist_id}","starred_url":"https://api.github.com/users/deni-zen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/deni-zen/subscriptions","organizations_url":"https://api.github.com/users/deni-zen/orgs","repos_url":"https://api.github.com/users/deni-zen/repos","events_url":"https://api.github.com/users/deni-zen/events{/privacy}","received_events_url":"https://api.github.com/users/deni-zen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-02T05:56:39Z","updated_at":"2016-08-02T05:56:39Z","closed_at":null,"body":"I need to write a document outlining all of my git policies and processes. For instance... \r\n\r\n- how do I branch and merge when it comes to development branches, version push branches (v0.1/master, v0.1/features-63, v1/master, beta/master, etc.). \r\n- Read up on the various common git workflows and decide on the best one for this particular project (keeping in mind you may eventually have additional developers). \r\n- document how to branch and merge for feature additions, bug fixes, etc. \r\n- how to associate a branch with a particular github issue #. \r\n- Document best practices for git commit messages and include a default template to be used by developers working on the project. Etc. etc. "}}
{"actor":{"display_login":"deni-zen"}}