.github/backstage_yaml: Remove catalog generator#2042
Open
Conversation
Used to create components for HDL libraries and projects with dependency hierarchy. However, the level of granularity overfitted the compliance purpose. A representing a tag as a component for all projects and libraries is more straightforward than a component per project/library per tag. Signed-off-by: Jorge Marques <jorge.marques@analog.com>
gastmaier
requested review from
AndreiGrozav,
PopPaul2021,
acostina and
sarpadi
as code owners
Contributor
Author
|
@acostina to remove the backstage branch, we need to remove the workflow file, or it just comes back at the next merge |
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
1 participant
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.
PR Description
Used to create components for HDL libraries and projects with dependency hierarchy. However, the level of granularity overfitted the compliance purpose. A representing a tag as a component for all projects and libraries is more straightforward than a component per project/library per tag.
PR Type
PR Checklist