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
{{ message }}
This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
Thanks for the fantastic library! I just got this setup as a GH action which then immediately pushes the changes to the branch it runs on. Works like a charm.
However, I just noticed that the output is rather noisy - running the command on a repo that already had a docs folder results in a 44k line difference, all little things like changing the time of the generated output, etc. Is there a way to disable that? As you can imagine, it makes reviewing PRs difficult because now we have to sift through all of the regenerated changes. In a best case scenario, I think the command should change nothing in the docs folder if the documentation in the actual code didn't choose.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
Thanks for the fantastic library! I just got this setup as a GH action which then immediately pushes the changes to the branch it runs on. Works like a charm.
However, I just noticed that the output is rather noisy - running the command on a repo that already had a
docs
folder results in a 44k line difference, all little things like changing the time of the generated output, etc. Is there a way to disable that? As you can imagine, it makes reviewing PRs difficult because now we have to sift through all of the regenerated changes. In a best case scenario, I think the command should change nothing in thedocs
folder if the documentation in the actual code didn't choose.The text was updated successfully, but these errors were encountered: