{"action":"opened","issue":{"url":"https://api.github.com/repos/gradle/kotlin-dsl/issues/921","repository_url":"https://api.github.com/repos/gradle/kotlin-dsl","labels_url":"https://api.github.com/repos/gradle/kotlin-dsl/issues/921/labels{/name}","comments_url":"https://api.github.com/repos/gradle/kotlin-dsl/issues/921/comments","events_url":"https://api.github.com/repos/gradle/kotlin-dsl/issues/921/events","html_url":"https://github.com/gradle/kotlin-dsl/issues/921","id":330074166,"node_id":"MDU6SXNzdWUzMzAwNzQxNjY=","number":921,"title":"gradle/kotlin-dsl and gradle/gradle should use the same branching scheme","user":{"login":"adammurdoch","id":99316,"node_id":"MDQ6VXNlcjk5MzE2","avatar_url":"https://avatars2.githubusercontent.com/u/99316?v=4","gravatar_id":"","url":"https://api.github.com/users/adammurdoch","html_url":"https://github.com/adammurdoch","followers_url":"https://api.github.com/users/adammurdoch/followers","following_url":"https://api.github.com/users/adammurdoch/following{/other_user}","gists_url":"https://api.github.com/users/adammurdoch/gists{/gist_id}","starred_url":"https://api.github.com/users/adammurdoch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adammurdoch/subscriptions","organizations_url":"https://api.github.com/users/adammurdoch/orgs","repos_url":"https://api.github.com/users/adammurdoch/repos","events_url":"https://api.github.com/users/adammurdoch/events{/privacy}","received_events_url":"https://api.github.com/users/adammurdoch/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-07T00:10:13Z","updated_at":"2018-06-07T00:10:13Z","closed_at":null,"author_association":"MEMBER","body":"Using different approaches and conventions for a common problem in each of our repositories means extra friction for developers moving between these repositories, particularly on the first use of a given repo. It also means more cost in whatever automation we use as this automation has to account for these differences. And so, the differences have to be justified by some strong benefit that outweighs the costs. I can't see any real benefit in this case (branching scheme) so we should get rid of the differences.\r\n\r\n### Expected Behavior\r\n\r\n`gradle/gradle` and `gradle/kotlin-dsl` (and `gradle/gradle-native` and the guides infrastructure and ...) all use the same branching scheme. I don't particularly care which scheme that happens to be, but I do care that it's the same everywhere.\r\n\r\n### Current Behavior\r\n\r\nBranching schemes are different.\r\n"}}
{"actor":{"display_login":"adammurdoch"}}