-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature suggestion: allow more flexibility in github release source fact for monorepos #3800
Comments
Thanks for suggesting. I agree that more flexibility would be awesome, but sadly, GitHub's Latest Release endpoint will always return the latest release and doesn't allow for filtering. For a detailed explanation, see #2943 (comment) Related: |
OK. Would it be possible to just have an option to not show any repo facts instead, or to show something custom? I guess it's possible to do this by creating an override, but I figure this might be a somewhat common issue. |
Hiding the tag is easy with a few lines of CSS, as noted in #2481 (comment). I'm not keen on adding another option which we'd have to hand over from |
OK, thanks! |
Before: ![image](https://user-images.githubusercontent.com/4010439/176032411-17f6ada2-bfbf-4562-ae79-ec6e845698ae.png) After: ![image](https://user-images.githubusercontent.com/4010439/176032474-8d9d7e26-a921-4199-a5fa-8b05b387ee71.png) (that will be `iree-org/iree` after #9635) References: * https://squidfunk.github.io/mkdocs-material/setup/changing-the-colors/#color-palette-toggle (that lists other popular icon combinations) * https://squidfunk.github.io/mkdocs-material/setup/adding-a-git-repository/ (and squidfunk/mkdocs-material#3800 (comment))
Contribution guidelines
I want to suggest an idea and checked that ...
Description
Currently, source facts are derived from GitHub, including the current release. For monorepos, releases for multiple packages might be published to the same github repo. It would be nice to provide some kind of filtering mechanism to Material so that only releases matching a certain package or string or regex would be included in the source fact.
I encountered this issue while trying to make a new docs system for appium. The release tag which is shown is for a package unrelated to the one I am publishing docs for.
Use Cases
This would benefit monorepo users or those who might want flexibility over which release/tag is shown in the documentation (not simply the first returned by GitHub).
Screenshots / Mockups
The text was updated successfully, but these errors were encountered: