Skip to content

Commit 90db3cc

Browse files
authored
[docs] Add a step to API docs publishing about flipping monikers from 'prelease' to 'live'. (#24465)
Also fix some markdown formatting.
1 parent da15dbc commit 90db3cc

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

docs/update-api-docs.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,9 @@ The steps are:
4747

4848
Once this pull request has been merged, an automated publishing job will get any changes in the `main` branch into the `live` branch, which will then show up on https://learn.microsoft.com.
4949

50-
7. The last step is to create a pull request in the [binaries](https://apidrop.visualstudio.com/_git/binaries) repository for the `netX.Y-xcodeZ.W` we created with the new assemblies (into the `master` branch).
50+
7. Create a pull request in the [binaries](https://apidrop.visualstudio.com/_git/binaries) repository for the `netX.Y-xcodeZ.W` we created with the new assemblies (into the `master` branch).
51+
52+
8. The final step is to flip the monikers from prerelease to live monikers (another ticket has to be created for this).
5153

5254
## How to create new monikers
5355

@@ -67,13 +69,15 @@ So for the initial .NET 10 release, when we shipped APIs for iOS 26.0, tvOS 26.0
6769
We can't create monikers ourselves, we have to request their creation:
6870

6971
1. Go here: [Learn Request Central](https://microsoft.sharepoint.com/teams/Partnerships/SitePages/Learn%20Request%20Central.aspx) (you might have to request access the first time you go here)
70-
a. Under "GitHub Publishing Services" click [Submit your request](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRxxUz-ZV53lLrgTaBjGRmtBUNlkzT01CSzNBSE1SRU8yRzU5UTZFNjQyOC4u)
71-
b. Fill in the form with:
72+
1. Under "GitHub Publishing Services" click [Submit your request](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRxxUz-ZV53lLrgTaBjGRmtBUNlkzT01CSzNBSE1SRU8yRzU5UTZFNjQyOC4u)
73+
2. Fill in the form with:
7274
1. I am working on publishing a new content set.
7375
2. I need help with updating information architecture (IA) or navigation.
7476
3. Request monikers.
7577
This will lead you to a template to fill an issue. Here's a sample of how I filled it out once: [#480959](https://dev.azure.com/msft-skilling/Content/_workitems/edit/480959).
7678

79+
Note: monikers are typically created as prerelease monikers. Another request has to be created to flip them to live monikers once everything else is in place.
80+
7781
It can be helpful to view info about all monikers here: [All monikers](https://ops.microsoft.com#/monikers)
7882

7983
## References

0 commit comments

Comments
 (0)