build status and coverage badges should be relative paths

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Right now, the README.md files show badgets pointing to a hardcoded branch, ie:

![Build Status](/../badges/master/pipeline.svg)
![Coverage](/../badges/master/coverage.svg)

That code shows the buld status and coverage for the master branch, but if I switch to another branch, it will still show the badges to the master branch.

The goal is to have relative paths so they show the right badge for the current branch. This could make it easier for users to adopt and help increase the number of users using badges in their README files.

Intended users

• Parker (Product Manager)
• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)
• Sam (Security Analyst)
• Dana (Data Analyst)

Proposal

My proposal is to be able to use relative paths and they should point to the badge of the current branch (or tag)

![Build Status](badges/pipeline.svg)
![Coverage](badges/coverage.svg)

Notice: it's very common to name a branch as a subfolder, like feature/gl-123-relative-paths-for-badges, this could also be a problem. to keep in mind.