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

use configured area order #273

Merged
merged 4 commits into from
Nov 7, 2023
Merged

Conversation

BillWagner
Copy link
Member

Instead of sorting the configured areas in alphabetical order, use the order specified in the whatsnew.json file.

Fixes #271

Instead of sorting the configured areas in alphabetical order, use the order specified in the whatsnew.json file.

Fixes dotnet#271
BillWagner added a commit to BillWagner/docs that referenced this pull request Nov 6, 2023
See dotnet/docs-tools#273

I used this order to test that PR.

I grouped sets of areas as follows:

- Changes all readers should know about (security, breaking changes)
- Fundamentals
- Languages
- Architecture
- Workloads / libraries
- Windows only .NET Framework
Transfer the quick and dirty messages I was using to help another team member to messages that will help everyone in the future.
@BillWagner BillWagner merged commit 8ecf605 into dotnet:main Nov 7, 2023
9 checks passed
@BillWagner BillWagner deleted the use-configured-areas branch November 7, 2023 20:31
BillWagner added a commit to dotnet/docs that referenced this pull request Nov 9, 2023
See dotnet/docs-tools#273

I used this order to test that PR.

I grouped sets of areas as follows:

- Changes all readers should know about (security, breaking changes)
- Fundamentals
- Languages
- Architecture
- Workloads / libraries
- Windows only .NET Framework
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.

[Whats New] - Use config file order for ordering sections
2 participants