Markup: Placeholder for branch name in readme.md file

[borismod]

Readme.md file usually contains badges of external tools, like CI, code coverage etc. These badges consist of an image and a link. Both the image and the link contain a branch in order to represent the current status of the branch.

An example of such badge:

I would like to be able to specify a placeholder of a branch name and it would be automatically replaced with the current branch.

[0xced]

I think your best option is to use a pre-commit hook to update the badges.

[borismod]

Thank you for your reply. It seems like a good workaround. I manage many
repositories and handle these hooks would be tedious. I would prefer a
placeholder for the current branch.
On Jul 12, 2016 11:34 PM, "Cédric Luthi" [email protected] wrote:

I think your best option is to use a pre-commit hook
http://stackoverflow.com/questions/18673694/referencing-current-branch-in-github-readme-md/35368808#35368808
to update the badges.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/github/markup/issues/913#issuecomment-232171704, or mute
the thread
https://github.com/notifications/unsubscribe/AAM0M8GoYcKiN5b_85HJEaFZQu0YWuFpks5qU_pMgaJpZM4JKU-D
.

[kobalicek]

This is finally a good idea to solve this problem, I think everybody who has more than one branch is dealing with this issue and precommit hooks are not the solution. To be honest I would like to see more placeholders so I can add there organization and repository as well, so when somebody forks the repo he wouldn't see "green".

From the development perspective I really don't see any obstacles here, it's a very noninvasive addition to the markdown.

[borismod]

@kobalicek I agree with placeholders for user/organization name as well. It would be really great!

[kobalicek]

@borismod I guess we only need more people to support this issue and it will get implemented, right :)?

[wakatta]

:+1:

[mrexodia]

:+1:

[refi64]

:+1:

[1forh]

👍

[andreassiegel]

👍

[Miljar]

👍

[gaborbernat]

:+1:

[carlosds730]

I support it!

[sc0ttkclark]

Related: #472, #101, #84, this is a recurring request :)

I'd love it though!

[nicolargo]

Need that ! +1

[gborri]

+1

[jkribeiro]

+1

[csoltenborn]

👍

[Headcult]

Much needed feature for showing branch respective badges in Github Readme. Any update on this request?

[mmitche]

+1

[qiuzuhui]

+1

[okutane]

Another cool feature would be the possibility to also replace user and repository name in the badge URL, so repo works could have their own badges without updates to readme.md.

[chriskirkland]

👍

[saromleang]

👍

[kivikakk]

Per https://github.com/github/markup/issues/472#issuecomment-97765976, the filters aren't part of github-markup, so there isn't a change we could make here that would fix this issue.

Please reach out to support to make sure your feature requests are considered appropriately! Thanks. :)

[kobalicek]

Please reach out to support? You are kidding me...

[kivikakk]

@kobalicek: the Markup gem has nothing to do with the requested feature, and the Support team is the one responsible for tallying feature requests, not the engineers working on GitHub's HTML pipeline. I hope this makes sense!

[kobalicek]

@kivikakk If you ever cared you would have reached the channels before closing this issue and linked it here so we can continue the discussion at appropriate place. If this was not appropriate feature request it should have been closed immediately and not rotting here for months. I really thought this would be resolved as I really think this is important.

[OmgImAlexis]

If this is to be closed we should be directed to a PUBLIC place we can talk about these instead of just being told to "contact support" as we all know that doesn't actually do anything. Github is meant to be able public code sharing and helping others out not shoving each other into private areas where nothing happens.

[deksden]

Not first time, but idea is old: https://github.com/github/markup/issues/472

Seems strange to me, why not implemented yet - not so difficult to implement. It would be extremely useful to anybody with CI, Greenkeeper or some coverage report stuff on repo.

@kivikakk : Please, redirect /send link to this thread to proper place / men / department / email to increase chance to implement this feature

upd2: Sent feature request to support

upd3: replay from support:

...
I can't make any promises, but I'll let the appropriate teams know that you'd like to see us add this in the future.
...

[AlexShemeshWix]

+1

[kobalicek]

I'm giving up, no more notifications about this. Github apparently doesn't have the manpower to implement a stupid text replacement feature, so thank you github, for nothing!

[marcelstoer]

To all of you wanting this so badly as I do: have you spent 3min sending a request to https://github.com/contact already? I'm frustrated as well but that's the only thing I could do.

[OmgImAlexis]

@marcelstoer yes, the first time I did I was told to open an issue in this repo and the second I was told "we'll pass the feedback on to our developers" and that was a few months ago... 😞

[niconoe-]

+1

And I also sent a request through the contact form.

[calebolin]

I sent a request as well. Not holding my breath for this to make it into Enterprise. :(

[ghost]

+1

[iDaN5x]

+1

[davidrdark]

+1

[GuilhermeMorais]

+1

[martin-walsh]

+1

[kivikakk]

This has already been directed (several times) to the appropriate departments. We're thinking about this, as ever, but it's non-trivial due to (among other things) how Camo's caching works. +1 comments are really not helpful, so I'm locking the conversation now.