{"action":"created","issue":{"url":"https://api.github.com/repos/github/markup/issues/472","labels_url":"https://api.github.com/repos/github/markup/issues/472/labels{/name}","comments_url":"https://api.github.com/repos/github/markup/issues/472/comments","events_url":"https://api.github.com/repos/github/markup/issues/472/events","html_url":"https://github.com/github/markup/issues/472","id":64148546,"number":472,"title":"[Question] reference current branch in markdown","user":{"login":"vors","id":816680,"avatar_url":"https://avatars.githubusercontent.com/u/816680?v=3","gravatar_id":"","url":"https://api.github.com/users/vors","html_url":"https://github.com/vors","followers_url":"https://api.github.com/users/vors/followers","following_url":"https://api.github.com/users/vors/following{/other_user}","gists_url":"https://api.github.com/users/vors/gists{/gist_id}","starred_url":"https://api.github.com/users/vors/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vors/subscriptions","organizations_url":"https://api.github.com/users/vors/orgs","repos_url":"https://api.github.com/users/vors/repos","events_url":"https://api.github.com/users/vors/events{/privacy}","received_events_url":"https://api.github.com/users/vors/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-25T01:55:47Z","updated_at":"2015-05-29T17:08:29Z","closed_at":"2015-04-30T13:00:47Z","body":"This question/proposal relates to well-known problem:\r\n[How I can embed CI badge for the **current** branch?](http://stackoverflow.com/questions/18673694/referencing-current-branch-in-github-readme-md)\r\n\r\nI tried solve it for my projects and I don't see an acceptable solution.\r\nCurrent options lent to one of the two things:\r\n1.  You have to hardcode different branche names in different branches and have a pain on every merge.\r\n2.  You report status for fixed number of branches in a table. Then you don't have badges for short-living branches (like feature branches in gitflow).\r\n\r\nAcceptable solution can be done, if we tweak github markdown processing, for instance during  [autolinking](https://github.com/jch/html-pipeline/blob/master/lib/html/pipeline/autolink_filter.rb), since it's very close spiritually. :)"},"comment":{"url":"https://api.github.com/repos/github/markup/issues/comments/106873113","html_url":"https://github.com/github/markup/issues/472#issuecomment-106873113","issue_url":"https://api.github.com/repos/github/markup/issues/472","id":106873113,"user":{"login":"sc0ttkclark","id":709662,"avatar_url":"https://avatars.githubusercontent.com/u/709662?v=3","gravatar_id":"","url":"https://api.github.com/users/sc0ttkclark","html_url":"https://github.com/sc0ttkclark","followers_url":"https://api.github.com/users/sc0ttkclark/followers","following_url":"https://api.github.com/users/sc0ttkclark/following{/other_user}","gists_url":"https://api.github.com/users/sc0ttkclark/gists{/gist_id}","starred_url":"https://api.github.com/users/sc0ttkclark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sc0ttkclark/subscriptions","organizations_url":"https://api.github.com/users/sc0ttkclark/orgs","repos_url":"https://api.github.com/users/sc0ttkclark/repos","events_url":"https://api.github.com/users/sc0ttkclark/events{/privacy}","received_events_url":"https://api.github.com/users/sc0ttkclark/received_events","type":"User","site_admin":false},"created_at":"2015-05-29T17:08:29Z","updated_at":"2015-05-29T17:08:29Z","body":"Yeah I really want to see this too. I'll e-mail, maybe I might be just a second e-mail about the subject but at least it's better than none."}}