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
The medium-term goal in-lieu of swimm is for the docs repo to have all the projects it covers (defra, orbis, lens, etc...) work as git-submodules, and the GithubActions system provide automation to notify if/when something falls out of sync. Then ensuring that each "codeblock" or something in the public docs, is linked to a specific Line(s) of code, so if the code changes (in a meaninful way) on the source repo, then we get visibility/automation on the docs repo.
Swimm is nice because all the platform metadata for linking docs/code was embedded as markdown data. Possibly extend that
The text was updated successfully, but these errors were encountered:
Use AST semantics within the diff algorithm for submodule comparison to tracking meaningful changes (and non-changes), to better couple the docs and code
John's idea:
The medium-term goal in-lieu of swimm is for the docs repo to have all the projects it covers (defra, orbis, lens, etc...) work as git-submodules, and the GithubActions system provide automation to notify if/when something falls out of sync. Then ensuring that each "codeblock" or something in the public docs, is linked to a specific Line(s) of code, so if the code changes (in a meaninful way) on the source repo, then we get visibility/automation on the docs repo.
Swimm is nice because all the platform metadata for linking docs/code was embedded as markdown data. Possibly extend that
The text was updated successfully, but these errors were encountered: