Automatically change branch name in README.md when creating new version branch

[boesing]

Feature Request

Q	A
New Feature	yes

Summary

Hey there,

in most laminas projects are badges for coveralls and travis build results. These badges point on builds for specific branches on travis/coveralls.

When laminas/automatic-releases kicks in, the branch is still pointing to the initial branch (which was probably set up when the package was created).

I'd like this tool to change the branch name in the README.md aswell so travis builds and coveralls stats are shown for the branch one is working on.

[Ocramius]

I think it would make more sense to run a small vadge proxy at that point? Committing changes just for the badges seems too error prone, especially considering that badges format is not set in stone 🤔

[geerteltink]

Isn't there a service like shields.io or somthing which we can use to generate badges for the default / latest branch?

[Ocramius]

Related: badges/shields#5215

[geerteltink]

Ah, that's how they generate it without a branch. It would be nice if github would make the default branch accessible somehow. Something like https://github.com/laminas/automatic-releases/tree/default, if that is even technically possible.