Repository navigation
docs: drop modern-di integrations from the org profile and site - #128
Merged
Merged
Conversation
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.
The org profile and modern-python.org listed all 13
modern-di-*integrations, so the Dependency injection section was the longest on both pages. The integrations are now listed only on the modern-di docs site, and the DI section on both pages links there.The integrations keep their brand marks, because every integration README loads its lockup banner from
brand/projects/in this repo.The profile/manifest invariant now skips
modern-di-*repos. The DI table test expects exactlymodern-dithenthat-depends, and a new test fails if amodern-di-*link shows up again on the profile or the site homepage.scripts/check_site_content.shno longer expects the integration links.Checked locally with
uv run pytest(174 passed),uv run mkdocs build --strictandscripts/check_site_content.sh.