You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described there, sometimes there are commonalities between tech stacks across suborg definitions, which can result in a lot of duplication and thus drift. In that issue it was noted that being able to have multiple suborgs apply configurations has innate challenges because of how that data is processed.
It would be helpful to be able to have standardized configurations in separate files that could be imported, akin to say "frontend_labels.yml", "backend_rulesets.yml", "compliance_rulesets.yml", "jira_autolinks.yml", etc
Then, within suborgs, you could have something like:
Prerequisites:
n/a
n/a
New Feature
This was brought up in discussion in a previous issue, but that ended up taking a different direction.
As described there, sometimes there are commonalities between tech stacks across suborg definitions, which can result in a lot of duplication and thus drift. In that issue it was noted that being able to have multiple suborgs apply configurations has innate challenges because of how that data is processed.
It would be helpful to be able to have standardized configurations in separate files that could be imported, akin to say "frontend_labels.yml", "backend_rulesets.yml", "compliance_rulesets.yml", "jira_autolinks.yml", etc
Then, within suborgs, you could have something like:
The text was updated successfully, but these errors were encountered: