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
I see no real alternative either. Doesn't moving parts of our docs + testing elsewhere simply shift the problem around? That new place will still need testing, whenever things change. No difference.
Except code + docs in one place (=now) makes more sense conceptually IMO.
Yes, scripts / hooks that verify docs are in-sync, preferably at PR merge-time, would be nice.
During each PR build, our CI scripts should check that the autogenerated files are in sync with their parents. If they are out of sync, the CI build should crash. The PR author should then bring the files up to date and add them to the PR.
I see no real alternative either. Doesn't moving parts of our docs + testing elsewhere simply shift the problem around? That new place will still need testing, whenever things change. No difference.
Except code + docs in one place (=now) makes more sense conceptually IMO.
Yes, scripts / hooks that verify docs are in-sync, preferably at PR merge-time, would be nice.
Originally posted by @piskvorky in #2907 (comment)
The text was updated successfully, but these errors were encountered: