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
Also, since netlify runs the build step on Linux, I would have expected that the sudoers reference page would be removed now. I don't understand why it claims (in GitHub actions) there were no changes. Maybe it does not detect when a page is being deleted?
When I run make docsy locally on Linux, then the sudoers page is no longer generated.
Which means with the current setup we will not have documentation for commands that are not included on Linux. So it might be better to always add them, and have them output The foo is not supported on this platform than just removing them.
I think that error is less confusing to the user than
FATA[0000] unknown command "foo" for "limactl"
when the online docs claim that the command exists.
The text was updated successfully, but these errors were encountered:
In the long term, it might be better to update the docs to display slightly different information depending on the platform. The pkg.go.dev already does this:
#3425 removed the
sudoers
command from Linux and Windows.The
start-at-login
command was never available on Windows.The docs should note these restrictions:
Also, since netlify runs the build step on Linux, I would have expected that the
sudoers
reference page would be removed now. I don't understand why it claims (in GitHub actions) there were no changes. Maybe it does not detect when a page is being deleted?When I run
make docsy
locally on Linux, then thesudoers
page is no longer generated.Which means with the current setup we will not have documentation for commands that are not included on Linux. So it might be better to always add them, and have them output
The foo is not supported on this platform
than just removing them.I think that error is less confusing to the user than
when the online docs claim that the command exists.
The text was updated successfully, but these errors were encountered: