Add boilerplate info about how to get support and provide feedback. #680

kbrandl · 2019-01-17T23:02:30Z

Also, disable the OPS "feedback" feature.

Note: this PR adds boilerplate to all files except for files in the /api folder (a separate PR will update those files).

…e to reference that article; turn off the feedback feature for the doc set.

1. Removed bold formatting on table heading, which interferes with the OPS heading style (the OPS style is a darker black that is different from the bold black). 2. Updated VBA-Docs (from lowercase "docs") to reflect actual repo name 3. Removed en-us from links so they go to localized pages (if any) 4. Added breaks where necessary to improve readability

…uery-language.

…s-shapes.

…cations.

opbld32 · 2019-01-17T23:02:37Z

OPS Build status updates of commit a974700:

🕙 Preparing: average preparing time is 3 min(s) 15 sec(s)

opbld33 · 2019-01-17T23:07:08Z

OPS Build status updates of commit a974700:

🕙 Full build: average full build time is not available, there is no data for this repository.

Note: A full build takes more time than an incremental build. This is the expected behavior of the build system.

kbrandl · 2019-01-17T23:09:24Z

@Linda-Editor here's the PR that adds the new boilerplate support/feedback content at the bottom of every file (and disables the OPS "feedback" feature). I've requested your review so that you can spot-check these changes. To do so, I'd suggest you take a look at the changes in several of the commits that this PR contains (for example: fed1c6e).

The only type of change that you should see in each file is adding the [!include[Support and feedback](~/includes/feedback-boilerplate.md)] statement at the end of the file (sometimes extra blank lines are also added or removed near this statement -- but that's expected).

Please do not merge this PR to master until you hear from me later today. I'm waiting for the OPS build to finish so that I can verify that everything looks okay on the staging site.

Linda-Editor · 2019-01-17T23:12:09Z

@kbrandl Thanks, Kim, but where did you want me to check it? I can't access staging with my current perms (for 6 months I'm off corp-net). So the only place I can see these is in the GitHub UI, I think. Or I suppose I can clone GitHub and view your branch that way (in Visual Studio Code). Would that work?

Linda-Editor · 2019-01-17T23:15:39Z

@kbrandl I looked at the GitHub change file that you linked to above, and everything looks good on that.

kbrandl · 2019-01-17T23:16:36Z

@Linda-Editor you should use the GitHub UI to spot check the changes.

Within this PR, click the Commits tab:
From the Commits page, click the link for any of today's commits:
Within each commit, the only type of change that you should see in each file is adding the [!include[Support and feedback](~/includes/feedback-boilerplate.md)] statement at the end of the file (sometimes extra blank lines are also added or removed near this statement -- but that's expected).

Check several commits, and if you see any types of changes other than the new [!include[Support and feedback](~/includes/feedback-boilerplate.md)] statement (and blank lines added or removed) at the end of the file, let me know by commenting here. (There are 90 commits -- you don't need to review them all -- just randomly pick 10-15 to check.)

Linda-Editor · 2019-01-17T23:18:24Z

@kbrandl Okay, will do.

Linda-Editor · 2019-01-17T23:26:29Z

@kbrandl I randomly selected about 10 sets and scanned them, and all look good...

kbrandl · 2019-01-17T23:28:29Z

@Linda-Editor thank you for reviewing -- can you please mark this PR as "Approved"? I will merge it to master after I'm able to verify changes on the staging site later today (build has been running for 2+ hours).

BTW -- I see that Linda Lu has merged other PRs to master within the last hour. Can you please tell her to stop working in this repo (and to not 'publish to live' today)? Thanks.

Linda-Editor · 2019-01-17T23:38:44Z

@kbrandl I let Linda Lu know as soon as I saw that she did that, and she reverted the one PR she merged.

opbld34 · 2019-01-18T02:41:29Z

OPS Build status updates of commit a974700:

❌ Validation status: errors

File	Status	Preview URL	Details
api/TOC.md	❌Error		Details

api/TOC.md

[Error] W:\tuio-s\api\TOC.md is not a valid TOC File: Invalid toc file: W:\tuio-s\api\TOC.md, Details: Unknown syntax at line 37743:
[!includeSupport and feedback]
[Error] Unable to load file 'api/TOC.md' via processor 'TocDocumentProcessor': W:\tuio-s\api\TOC.md is not a valid TOC File: Invalid toc file: W:\tuio-s\api\TOC.md, Details: Unknown syntax at line 37743:
[!includeSupport and feedback]
[Error] W:\tuio-s\api\TOC.md is not a valid TOC File: Invalid toc file: W:\tuio-s\api\TOC.md, Details: Unknown syntax at line 37743:
[!includeSupport and feedback]
[Error] Unable to load file 'api/TOC.md' via processor 'ExperimentalTocDocumentProcessor': W:\tuio-s\api\TOC.md is not a valid TOC File: Invalid toc file: W:\tuio-s\api\TOC.md, Details: Unknown syntax at line 37743:
[!includeSupport and feedback]

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

This reverts commit a974700.

opbld30 · 2019-01-18T02:55:39Z