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
there are a few cases in the docs where yaml files are literalincluded
if they don't include all lines, or if some lines are emphasized this can break when the yaml files change
this is kinda brittle - but theres not an easy way to prevent - although we may be able to add some indexing of relevent files/lines and expected content which could potentially trigger a fail in ci when the expectations are no longer met
in the meantime, its important when reviewing config files that are included in this way to check if the change impacts the docs
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
phlax
added
no stalebot
Disables stalebot from closing an issue
and removed
stale
stalebot believes this issue/PR has not been touched recently
labels
May 14, 2021
description
there are a few cases in the docs where
yaml
files areliteralincluded
if they don't include all lines, or if some lines are emphasized this can break when the yaml files change
this is kinda brittle - but theres not an easy way to prevent - although we may be able to add some indexing of relevent files/lines and expected content which could potentially trigger a fail in ci when the expectations are no longer met
in the meantime, its important when reviewing config files that are included in this way to check if the change impacts the docs
The text was updated successfully, but these errors were encountered: