Skip to content

Create config and infrastructure for a What's new in docs for a release #30545

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

Merged
merged 23 commits into from
Nov 9, 2022

Conversation

BillWagner
Copy link
Member

@BillWagner BillWagner commented Aug 9, 2022

I think there are a number of tasks to use the what's new tool to generate a New docs for .NET 7 page:

  • Add a new config file
  • Add the ".NET 7 Release" label to all pertinent PRs.
  • Create TOC and Index locations to put the new release-based article
  • Update the title and filename for the new release-based article
  • Update config section to create a release-based section for what's new.
  • Create a shell script (or an action) to create a release based article when requested.

Internal review link

@dotnet-bot dotnet-bot added this to the August 2022 milestone Aug 9, 2022
@BillWagner BillWagner requested a review from gewarren August 9, 2022 21:19
@BillWagner
Copy link
Member Author

I can test the project locally running the following command from the root of my local copy.

dotnet whatsnew --owner dotnet --repo docs --savedir .\docs\whats-new --startdate 11/01/2021 --enddate 11/09/2022 --localconfig .\.whatsnew.release.json

@gewarren
Copy link
Contributor

@BillWagner How can I help with this? Do you want me to add the labels to the PRs?

Copy link
Member Author

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

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

Add notes from email conversation.

@BillWagner BillWagner force-pushed the whats-new-net-7 branch 2 times, most recently from 0e51f44 to 6a1ece4 Compare November 8, 2022 18:28
@BillWagner BillWagner marked this pull request as ready for review November 8, 2022 20:09
@BillWagner BillWagner requested a review from a team as a code owner November 8, 2022 20:09
Copy link
Member Author

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

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

This should be mostly ready to go.

@gewarren I added a few comments where we may be able to trim this page more. Let me know your thoughts, and I'll continue making updates.

@BillWagner BillWagner enabled auto-merge (squash) November 9, 2022 17:50
@BillWagner BillWagner disabled auto-merge November 9, 2022 17:54
BillWagner and others added 23 commits November 9, 2022 12:59
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Use a large value to catch branch merge on what's new in the release.
The PR that merges .NET 7 features changed a lot of files.
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
@BillWagner BillWagner merged commit 8500268 into dotnet:main Nov 9, 2022
@BillWagner BillWagner deleted the whats-new-net-7 branch November 9, 2022 18:04
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