-
Notifications
You must be signed in to change notification settings - Fork 349
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
docs/technical: add an aspirational Git submodules doc #1411
Conversation
690e6c1
to
0cb25c2
Compare
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.
Here are some initial comments.
21bcfdb
to
4d5e8c0
Compare
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.
Thanks!
Can we move the document from |
4d5e8c0
to
a378f2e
Compare
This document is meant to be a record of how we think about Git submodules (and not a _current_ implementation of submodules). We will fill it out incrementally as we get a clearer idea of what we want submodules to look like. As an initial version, I started with (IMO) the least controversial points: - We want to support most workflows Git submodules users are accustomed to. - A roadmap that allows us to incrementally roll out Git submodule functionality (instead of having to boil the ocean).
a378f2e
to
f876fa2
Compare
Add
docs/technical/git-submodules.md
to capture how we think about submodules, starting with (IMO) the least controversial parts:The doc isn't complete, we will add more details and discuss them as they come, e.g. there are no designs yet.
Contributes to #494
If applicable:
CHANGELOG.md