-
Notifications
You must be signed in to change notification settings - Fork 46
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 REQUEST] Add support for associating projects with multiple TAGs #777
Comments
Hi @mrbobbytables 👋 This shouldn't be a problem. Some notes to keep in mind:
FYI we have a feature that maps landscape categories/subcategories to TAGs. It's used to set a default TAG for an item when none is provided in the |
Awesome! Replying to comments in line below:
I think thats fine 👍
I think that'd be fine, especially as some TAGs are going away it'd be changing over time anyway. |
Closes #777 Signed-off-by: Sergio Castaño Arteaga <tegioz@icloud.com> Signed-off-by: Cintia Sánchez García <cynthiasg@icloud.com> Co-authored-by: Sergio Castaño Arteaga <tegioz@icloud.com> Co-authored-by: Cintia Sanchez Garcia <cynthiasg@icloud.com>
Related to cncf/landscape2#777 and cncf/landscape2#780 Signed-off-by: Cintia Sánchez García <cynthiasg@icloud.com>
This is ready @mrbobbytables. For reference, this change also affected the generation of the |
Related to cncf/landscape2#777 and cncf/landscape2#780 Signed-off-by: Cintia Sánchez García <cynthiasg@icloud.com>
Thanks! |
Currently there is a one-to-one mapping of CNCF TAG to project, however many projects actually span more than one TAG and may have multiple TAGs involved in their review when moving levels. As far as I can tell, the tag variable is only used for filters so hopefully a change like this would not be very disruptive.
Current:
Desired:
The text was updated successfully, but these errors were encountered: