Repository navigation
docs: label the CI badge with the repository name and list ascender-mcp - #341
Merged
Merged
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
cigamit
approved these changes
Oct 29, 2026
This file contains hidden or 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
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.
Two README changes that every Ascender repository is getting in the same pass.
CI badge
GitHub's own
badge.svgprints the workflow'sname:, so the badge readCI,DevelorUnit Testsdepending on the repository, with nothing saying which repository it belonged to. It is now a shields.io workflow status badge labelled with the repository name,<repo> CI, pointing at the same workflow and still showing its live result. Renaming the workflows instead would have renamed their checks too, which branch protection can depend on.The Ascender ecosystem
The table gains ascender-mcp, the MCP server that lets AI agents work with Ascender through its REST API. It sits after
ascender-collection, beside the other two API clients.