-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation: Add how to guides #864
Conversation
Codecov Report
@@ Coverage Diff @@
## master #864 +/- ##
==========================================
- Coverage 87.31% 85.02% -2.30%
==========================================
Files 164 164
Lines 2705 2705
Branches 295 295
==========================================
- Hits 2362 2300 -62
- Misses 272 326 +54
- Partials 71 79 +8
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
how-to-docker update
I wonder if (like in #862 ) we should use a symbolic link for the outputengine file rather than renaming. This one is less clear to me -- we don't have other documents pointing at it in its current location, and it is more of a user thing to do (as opposed to adding a checker which we expect to mostly be a developer thing to do). |
And the docker scan stuff is looking good. I'm guessing from the dangling header at the end that you're not done with that doc yet. |
Yes, for docker scan, I have written one way which is install and run I forget to draft PR. |
I have moved html template guide to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I might do a few North American English nitpicks in a separate commit later, but since that's more window dressing than substance let's get this merged first.
No description provided.