Adds the Developed in dejima badge, matching dejima PR #114: the same asset, the same markup, and the same placement — end of the opening block, before the first section heading.
The test would not have caught a broken badge
test/links.bats had a test for the README's image, and it only knew about <img src="...png">. The badge is markdown image syntax and an svg, so neither half of that assertion would have seen it. It would have gone on passing while pointing at nothing, which is the shape of failure this repository keeps finding in its own tests.
It now walks every image the README references in either syntax and either format, and requires at least two — so a README that loses one of them fails rather than passing on the strength of the other.
Checked by pointing the badge at a file that does not exist and watching the guard name it.
The same change is in dejima-ci-hardener, where test/links.bats is arriving in PR #15 and the badge rides along with it.
**Summary generated by LLM agent**
Adds the `Developed in dejima` badge, matching dejima PR #114: the same asset, the same markup, and the same placement — end of the opening block, before the first section heading.
## The test would not have caught a broken badge
`test/links.bats` had a test for the README's image, and it only knew about `<img src="...png">`. The badge is markdown image syntax and an svg, so **neither half of that assertion would have seen it**. It would have gone on passing while pointing at nothing, which is the shape of failure this repository keeps finding in its own tests.
It now walks every image the README references in either syntax and either format, and requires at least two — so a README that loses one of them fails rather than passing on the strength of the other.
Checked by pointing the badge at a file that does not exist and watching the guard name it.
The same change is in `dejima-ci-hardener`, where `test/links.bats` is arriving in PR #15 and the badge rides along with it.
The same badge and the same asset as dejima carries, placed where dejima places it: at the end of the opening block, before the first section heading.
test/links.bats only knew about <img src="...png">. The badge is markdown image syntax and an svg, so neither half of that test would have seen it - the assertion would have kept passing while pointing at nothing. It now walks every image the README references in either syntax and either format, and requires at least two so a README that lost one of them fails rather than passing with the other.
Checked by breaking the badge path and watching the guard name it.
branderson
approved these changes 2026-08-10 18:41:01 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary generated by LLM agent
Adds the
Developed in dejimabadge, matching dejima PR #114: the same asset, the same markup, and the same placement — end of the opening block, before the first section heading.The test would not have caught a broken badge
test/links.batshad a test for the README's image, and it only knew about<img src="...png">. The badge is markdown image syntax and an svg, so neither half of that assertion would have seen it. It would have gone on passing while pointing at nothing, which is the shape of failure this repository keeps finding in its own tests.It now walks every image the README references in either syntax and either format, and requires at least two — so a README that loses one of them fails rather than passing on the strength of the other.
Checked by pointing the badge at a file that does not exist and watching the guard name it.
The same change is in
dejima-ci-hardener, wheretest/links.batsis arriving in PR #15 and the badge rides along with it.