marttilaine
Joined 3 years ago
Karma
125
Submissions
19
Member since
Jun 20
Joined 3 years ago
https://github.com/shipmight/shipmight/blob/master/src/ARCHI...
At the top of each file there was a tree of links to other ARCHITECTURE.md-files in the repo, like this:
* ARCHITECTURE.md <- you are here
* backend/ARCHITECTURE.md
* backend/api/ARCHITECTURE.md
* backend/cli/ARCHITECTURE.md
* backend/ui/ARCHITECTURE.md
* backend/utils/ARCHITECTURE.md
* frontend/ARCHITECTURE.md
* internal-charts/ARCHITECTURE.mdhttps://helm-playground.com/ - https://github.com/shipmight/helm-playground
What would you imagine as the optimal AI workflow? Iassume it's more complex than just issuing commands like "move AWS-section under Infrastructure"?
There are definitely many projects where you don't need to understand every single aspect of the codebase to be able to contribute a meaningful fix or even a feature.
It benefits the contributor and the project if they have a simple pointer to e.g. where the application logic code is, or where the distribution-related code is, etc.