-
Notifications
You must be signed in to change notification settings - Fork 43
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
Repository cleanup #235
Repository cleanup #235
Conversation
🦙 MegaLinter status: ❌ ERROR
See detailed report in MegaLinter reports |
Tip for reviewers: clone the |
Now uses template proposed in Governance issue 124
Now meets Governance issue 124
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Kevsy, as we now have a ‘child’ repository, would it be appropriate to include the link to refer to the fact that the SED API is now in that new repository?
Thanks @javierlozallu good idea, and done: I have removed the SED YAML from the Edge Cloud repo and instead left a link to the SED repo. I have also made the fixes from your review (and @nicolacdnll 's review - thanks both) |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Agreed on call 30th April 2024 - repository is difficult to navigate and contains many legacy/inactive documents. It is also not closely following the CAMARA repository structure
Which issue(s) this PR fixes:
Fixes #234
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.