docs: fix broken "Current status" badges #5783
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Badge URLs were outdated (not in a format that "Create status badge" outputs function right now), causing them to be "stuck in the past". As a result, README shown both Angular E2E workflows as failing, where in fact they are running just fine!
|
Good catch, I didn't realize GH broke those urls 😯 |
merceyz
pushed a commit
that referenced
this pull request
Oct 21, 2023
**What's the problem this PR addresses?** Badge URLs were outdated (not in a format that "Create status badge" outputs function right now), causing them to be "stuck in the past". As a result, README shown both Angular E2E workflows as failing, where in fact they are running just fine! **How did you fix it?** Recreated all badges **Checklist** <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. (cherry picked from commit d181aa6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's the problem this PR addresses?
Badge URLs were outdated (not in a format that "Create status badge" outputs function right now), causing them to be "stuck in the past". As a result, README shown both Angular E2E workflows as failing, where in fact they are running just fine!
How did you fix it?
Recreated all badges
Checklist