Skip to content

Commit d038cd4

Browse files
authored
Merge pull request #28023 from microsoftgraph/author-api-docs-prompt-correct-changelog-guidance
Author API docs prompt - Correct changelog guidance
2 parents 9a3c27a + fbec940 commit d038cd4

1 file changed

Lines changed: 50 additions & 5 deletions

File tree

.github/prompts/author-api-docs.prompt.md

Lines changed: 50 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -79,11 +79,56 @@ After authoring documentation, update the appropriate changelog file in the `cha
7979
}
8080
```
8181

82-
**Step 3: Copy changelog records**
83-
- Copy the ChangeList records from the autogenerated changelog
84-
- Add them to the appropriate changelog file in the `changelog/` folder
85-
- Ensure the WorkloadArea and SubArea match the autogenerated file
86-
- Use "beta" for Version in Scenario 1, "v1.0" for Version in Scenario 2
82+
**Step 3: Copy the complete changelog record**
83+
- **IMPORTANT:** A changelog record is NOT just the ChangeList array. A complete changelog record consists of:
84+
- `ChangeList` array (containing individual change items)
85+
- `Id` (unique GUID for this set of changes)
86+
- `Cloud` (e.g., "Prod")
87+
- `Version` (e.g., "beta" or "v1.0")
88+
- `CreatedDateTime` (ISO-8601 DateTime)
89+
- `WorkloadArea` (e.g., "Security")
90+
- `SubArea` (may be empty string)
91+
92+
- **How to copy the record:**
93+
1. Open the autogenerated changelog file from `temp-docstubs/` (e.g., `changelog_*.json` or `Microsoft.*.json`)
94+
2. Locate the complete record object inside the `"changelog"` array (usually lines 3 to the closing brace of that object)
95+
3. Copy the ENTIRE record object, including:
96+
- Opening brace `{`
97+
- The complete `ChangeList` array with all its items
98+
- All metadata properties (`Id`, `Cloud`, `Version`, `CreatedDateTime`, `WorkloadArea`, `SubArea`)
99+
- Closing brace `}`
100+
4. Open the target changelog file in `changelog/{prefix}.json`
101+
5. Paste the complete record as the FIRST item in the `"changelog"` array (after the opening `[`)
102+
6. Ensure proper JSON formatting with commas between records
103+
104+
- **Example of what to copy (complete record):**
105+
```json
106+
{
107+
"ChangeList": [
108+
{
109+
"Id": "1e2218aa-5dbc-4c74-a0fe-1d06e90b451c",
110+
"ApiChange": "Property",
111+
"ChangedApiName": "newProperty",
112+
"ChangeType": "Addition",
113+
"Description": "Added the **newProperty** property...",
114+
"Target": "resourceName"
115+
}
116+
],
117+
"Id": "1e2218aa-5dbc-4c74-a0fe-1d06e90b451c",
118+
"Cloud": "Prod",
119+
"Version": "beta",
120+
"CreatedDateTime": "2026-01-07T08:37:50.5865153Z",
121+
"WorkloadArea": "Security",
122+
"SubArea": ""
123+
}
124+
```
125+
126+
- **DO NOT:**
127+
- Copy only the ChangeList items and insert them into an existing record
128+
- Modify the Id, CreatedDateTime, or other metadata from the autogenerated file
129+
- Create a new record structure manually
130+
131+
- **Result:** The changelog file should have the new record added at the beginning of the changelog array, with all subsequent records following it
87132

88133
### Common Process: Updating What's New
89134

0 commit comments

Comments
 (0)