Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The current repository structure is pretty difficult to handle for new contributors as-it deviate a lot from the default @backstage/create-app boiler plate. Having the Backstage app untracked in the repository complicates the collaboration when many developers are work on the code base.
What is the outcome that you are trying to reach?
Describe the solution you would like
Implement the Backstage Community Plugins repository structure and CI pipeline to managed the AWS Harmonix plugin release.
Leverage traditional directory layout generated by the @backstage/create-app and move plugins from backstage-plugins/plugins directory to the classic plugins directory.
Community Note
The current repository structure is pretty difficult to handle for new contributors as-it deviate a lot from the default
@backstage/create-app
boiler plate. Having the Backstage app untracked in the repository complicates the collaboration when many developers are work on the code base.What is the outcome that you are trying to reach?
Describe the solution you would like
Implement the Backstage Community Plugins repository structure and CI pipeline to managed the AWS Harmonix plugin release.
Envisionned repo layout
Describe alternatives you have considered
Leverage traditional directory layout generated by the
@backstage/create-app
and move plugins frombackstage-plugins/plugins
directory to the classicplugins
directory.Additional context
Relates to #116