Skip to content
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

CI Update #5878

Merged
merged 2 commits into from
Apr 4, 2018
Merged

CI Update #5878

merged 2 commits into from
Apr 4, 2018

Conversation

Rick-Anderson
Copy link
Contributor

@Rick-Anderson Rick-Anderson commented Apr 4, 2018

Fixes #5879

Copy link
Contributor Author

@Rick-Anderson Rick-Anderson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These look good to me

@Rick-Anderson
Copy link
Contributor Author

@cillroy changes look good to me. Let me know when I can merge this.

@Rick-Anderson Rick-Anderson merged commit 1832723 into master Apr 4, 2018
@Rick-Anderson Rick-Anderson deleted the markdig-migration branch April 4, 2018 23:51
@Rick-Anderson Rick-Anderson restored the markdig-migration branch April 5, 2018 00:48
Rick-Anderson added a commit that referenced this pull request Apr 5, 2018
This reverts commit 1832723.
@Rick-Anderson Rick-Anderson mentioned this pull request Apr 5, 2018
scottaddie added a commit that referenced this pull request Apr 6, 2018
* Update azure-apps-preview-notice.md (#5857)

* Link to .NET Core CLI publish command doc (#5864)

* Link to .NET Core CLI publish command doc

* Verbiage tweak

* fix typo (#5866)

* Update intro.md (#5869)

`classnameID` (where `classname` is the name of the class, such as `Student`) as the primary key. In `classnameID`, `classname` is the name of the class, such as `Student` in

* Update view-components.md (#5872)

altering range of code displayed to remove hanging closing } and closing table tag

* C13511:  Spaces should be replaced to avoid localization problems (#5871)

Hello, @Rick-Anderson, 

Localization team has reported source content issue that causes localized version to have broken format compared to en-us version.  

Please, help to check my proposed file change into the article and help to merge if you agree with fix. If not, please, let me know either if you would like me to fix it in another way within this PR, if you prefer to fix it in another PR or if I should close this PR as by-design. In case of using another PR, please, let me know of your PR number, so we can confirm and close this PR. 

Many thanks in advance.

* CI Update (#5878)

* Recommended language change (#5883)

* Updated with NET Core SDK 2.0  commands (#5886)

* Updated with NET Core SDK 2.0  commands

* Quick UE pass

* Prevent javascript injection. (#5885)

* Troubleshoot SDK warnings (#5880)

* WIP Troubleshoot SDK warnings

* Work

* work

* Address Gauntlet warning in ms.date value

* Adjust H2 title casing and spacing

* Quick UE pass

* Update Configuration doc to use double underscores instead of colons for hierarchical config keys (4968) (#5876)

* changes to configuration doc

* fixes for scott

* change for Dan

* Update index.md

* Code fence double underscore and add missing period

* Eliminate unnecessary sentence

* Missing npm task runner extension (#5893)

* Revert "Missing npm task runner extension (#5893)" (#5894)

This reverts commit a90faeb.

* Note about task runner explorer option (#5895)

* Note about task runner explorer option

The gulp file has to be in the root directory or in the directory with package.json not in any subdirectory.

* verbiage tweaks

* added anchored link (#5896)
@Rick-Anderson Rick-Anderson deleted the markdig-migration branch May 2, 2018 03:41
@guardrex
Copy link
Collaborator

@Rick-Anderson @scottaddie @rachelappel This PR converted the ends of tab markup from ...

---

to

* * *

I've been converting following this PR because I thought this was a new direction (and didn't ask 😢). I can switch back; but since this PR introduced a lot of * * * to the repo, do we need an issue to revert them?

I also think this was the PR that changed the tab hashes to four (####). I've been using this format ...

#### [ASP.NET Core 1.x](#tab/aspnetcore1x/)

Are we good on that approach going forward? ... four hashes?

@scottaddie
Copy link
Member

Here's how to determine the appropriate number of hashes for tabs: number of hashes = 1 + number of hashes used by parent heading

@rachelappel
Copy link
Contributor

Yeah, what should we do with the "* * *" - I noticed the dashes were magically converted to *'s on a couple of docs. I was changing them back. Thought it was just crap that got caught in there.

@guardrex
Copy link
Collaborator

number of hashes = 1 + number of hashes used by parent heading

That isn't being followed AFAIK by anyone here or on .NET docs. Here's a set of @mairaw changes (When you're doing something Maira, I consider that the GOLD STANDARD 🥇 in docs!) ... here's a set of changes where the tabs are being set they way they were originally explained to me ...

https://github.com/dotnet/docs/pull/4935/files

See line 82 ...

# [Visual Basic](#tab/vb)

... under a 3rd level heading (line 66) ...

### Tooling support for .NET Standard libraries

The training I received was one hash regardless of other headings. If that changed, 👍 gotcha; but it doesn't look like anyone knows.

@scottaddie
Copy link
Member

That's the training I received as well. Markdownlint says it's invalid. The issue is corrected when sticking with my suggested strategy.

@rachelappel
Copy link
Contributor

I noticed <em>'s that you changed in that Getting Started review @scottaddie. I had some of the same recently. What is sticking them in the docs, does anyone know? I had to change a few myself. It's like they appear randomly.

@guardrex
Copy link
Collaborator

Markdownlint says it's invalid

Aren't tabs a proprietary MS markdown feature? If so, I'd be surprised if Markdownlint is the source of truth for their implementation.

@scottaddie
Copy link
Member

Tabs are a custom Markdown extension. Since Markdownlint is bundled in the Docs Authoring Pack provided to external contributors, we should cleanup those warnings to set the precedent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants