payload: {"action":"created","issue":{"url":"https://api.github.com/repos/hawkowl/towncrier/issues/135","repository_url":"https://api.github.com/repos/hawkowl/towncrier","labels_url":"https://api.github.com/repos/hawkowl/towncrier/issues/135/labels{/name}","comments_url":"https://api.github.com/repos/hawkowl/towncrier/issues/135/comments","events_url":"https://api.github.com/repos/hawkowl/towncrier/issues/135/events","html_url":"https://github.com/hawkowl/towncrier/issues/135","id":388972787,"node_id":"MDU6SXNzdWUzODg5NzI3ODc=","number":135,"title":"RFC: parse git commit log for fragments","user":{"login":"refack","id":96947,"node_id":"MDQ6VXNlcjk2OTQ3","avatar_url":"https://avatars3.githubusercontent.com/u/96947?v=4","gravatar_id":"","url":"https://api.github.com/users/refack","html_url":"https://github.com/refack","followers_url":"https://api.github.com/users/refack/followers","following_url":"https://api.github.com/users/refack/following{/other_user}","gists_url":"https://api.github.com/users/refack/gists{/gist_id}","starred_url":"https://api.github.com/users/refack/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/refack/subscriptions","organizations_url":"https://api.github.com/users/refack/orgs","repos_url":"https://api.github.com/users/refack/repos","events_url":"https://api.github.com/users/refack/events{/privacy}","received_events_url":"https://api.github.com/users/refack/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-09T00:22:41Z","updated_at":"2019-12-29T10:49:07Z","closed_at":"2019-12-29T10:49:07Z","author_association":"NONE","body":"Seeking comments on a complimentary approach for extracting fragments - parse the git log for marked up parts. Similar to the approach used in nodejs/node (e.g. https://github.com/nodejs/node/commit/c3dd0d001abdb983d19987c76cad7ef30ef82a25).\r\nAs I imagine this:\r\n1. Author adds some marked up metadata to the commit message (`.feature: add foo to bar`)\r\n2. During release creating `towncrier` either infers the commit range, or is given manually\r\n3. `towncrier` parses message in commit range for fragments\r\n4. git fragments and file fragments lists are merged\r\n5. profit"},"comment":{"url":"https://api.github.com/repos/hawkowl/towncrier/issues/comments/569493946","html_url":"https://github.com/hawkowl/towncrier/issues/135#issuecomment-569493946","issue_url":"https://api.github.com/repos/hawkowl/towncrier/issues/135","id":569493946,"node_id":"MDEyOklzc3VlQ29tbWVudDU2OTQ5Mzk0Ng==","user":{"login":"hawkowl","id":3307100,"node_id":"MDQ6VXNlcjMzMDcxMDA=","avatar_url":"https://avatars0.githubusercontent.com/u/3307100?v=4","gravatar_id":"","url":"https://api.github.com/users/hawkowl","html_url":"https://github.com/hawkowl","followers_url":"https://api.github.com/users/hawkowl/followers","following_url":"https://api.github.com/users/hawkowl/following{/other_user}","gists_url":"https://api.github.com/users/hawkowl/gists{/gist_id}","starred_url":"https://api.github.com/users/hawkowl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hawkowl/subscriptions","organizations_url":"https://api.github.com/users/hawkowl/orgs","repos_url":"https://api.github.com/users/hawkowl/repos","events_url":"https://api.github.com/users/hawkowl/events{/privacy}","received_events_url":"https://api.github.com/users/hawkowl/received_events","type":"User","site_admin":false},"created_at":"2019-12-29T10:49:07Z","updated_at":"2019-12-29T10:49:07Z","author_association":"OWNER","body":"Towncrier explicitly doesn't do this for several reasons:\r\n\r\n- Git history is malleable and not trustworthy (e.g. if someone squash merges something by accident)\r\n- Merge commits are done at merge time, and not always by the person working on the actual task. This means that one has to do extra work to have the news text actually be part of the review, vs just part of the diff.\r\n- Things that check the newsfile then need a significant amount of history and can't be shallow clones.\r\n- uuuuuuuuuuuuuugh interfacing with git\r\n\r\nBut, yeah, it's designed to make it as separate as possible, as the person doing the git may not be the one writing the newsfile, It also means that you'd need to figure out which commit messages override which, which depends on your local tree if one cherry-picks a fix with a newsfile commit and then merges that in later. Also, editing newsfiles either means editing commits and force-pushing, or relying on the above \"which one has precedence\" figuring out in the git graph."}}
other: {"actor":{"display_login":"hawkowl"}}