Skip to content

Commit 304b241

Browse files
committed
Harpinder's prompt and the result
1 parent b54bc76 commit 304b241

File tree

2 files changed

+57
-110
lines changed

2 files changed

+57
-110
lines changed

changelog_prompt.md

Lines changed: 4 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,42 +1,5 @@
1-
# Prompt
1+
Please provide an API changelog from the following OASDiff of openapi spec changes. The output should be in markdown format grouping endpoints by use case/ object type. For cases where some schema is modified, please also tell what endpoints it affects.
22

3-
You are a technical writer creating release notes for an API.
4-
5-
## Target Audience
6-
The audience for the release notes consists of experienced developers who integrate the API into their applications. They rely on detailed documentation, advance notice of upcoming features, and clear information about potential breaking changes.
7-
8-
## Source Content Structure
9-
The changelog lists each endpoint that has changed and presents changes in a tree structure:
10-
- The most specific, actionable changes are found in the leaf nodes (deepest level) of each tree
11-
- Higher levels provide context but the actual modifications are at the leaves
12-
- When multiple endpoints show identical tree structures, they are receiving the same modification and should be grouped together
13-
- Every endpoint listed must be accounted for in the summary
14-
15-
## Analysis Guidelines
16-
When analyzing the changelog:
17-
1. Look carefully at the leaf nodes in each change tree
18-
2. Check if the change pattern matches other endpoints already documented
19-
3. Group similar changes together even if they appear in different parts of the changelog
20-
4. Never mark changes as "unspecified" - the specific modification is always in the leaf nodes
21-
5. Don't ask for clarification - instead, look more carefully at the patterns and leaf nodes
22-
23-
## Output Requirements
24-
1. Group changes by type (e.g., "New endpoints", "API Modifications") and then by shared modifications (e.g., "Sync metadata support", "Follow-up relationship support") rather than by endpoint
25-
2. Ensure every endpoint from the changelog is included in the summary
26-
3. Follow each tree to its leaves and document the specific change
27-
28-
## Style Rules
29-
1. Use sentence-case capitalization for headings and descriptions
30-
2. Avoid adjectives. Be plain and clear. This is technical documentation, not marketing material
31-
3. Be precise with endpoint and class names
32-
4. Keep the language concise and technical
33-
5. Ignore grammar/style changes in the changelog
34-
35-
## Markdown Syntax
36-
1. Use the header # Today's date for the title
37-
2. Use markdown headers (##, ###, ####) to structure the subheadings
38-
3. Link endpoints using [`endpoint.name`](/endpoint/name)
39-
4. Surround endpoints and fields in backticks
40-
5. Speak in second-person voice ("you") directly to developers
41-
42-
The generated changelog is attached to this request.
3+
<oasdiff>
4+
{{oasdiff}}
5+
</oasdiff>
Lines changed: 53 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -1,71 +1,55 @@
1-
# December 2, 2024
1+
# 2024-12-02
22

33
## New Endpoints
4-
- [`/dev-users.activate`](/beta/api-reference/dev-users/activate) - Activate a developer user
5-
- [`/dev-users.deactivate`](/beta/api-reference/dev-users/deactivate) - Deactivate a developer user
6-
7-
## API Modifications
8-
9-
### Article Scope Changes
10-
The `scope` parameter description was updated in:
11-
- [`/articles.count`](/beta/api-reference/articles/count) (GET and POST)
12-
- [`/articles.list`](/beta/api-reference/articles/list) (GET and POST)
13-
14-
### Parts Schema Updates
15-
Added `custom_schema_spec` field to request bodies in:
16-
- [`/parts.create`](/beta/api-reference/parts/create)
17-
- [`/parts.update`](/beta/api-reference/parts/update)
18-
19-
### Auth Connection Deprecations
20-
Marked Azure AD and Google Apps connection types as deprecated in:
21-
- [`/dev-orgs.auth-connections.create`](/beta/api-reference/dev-orgs/auth-connections/create)
22-
- [`/dev-orgs.auth-connections.get`](/beta/api-reference/dev-orgs/auth-connections/get)
23-
- [`/dev-orgs.auth-connections.list`](/beta/api-reference/dev-orgs/auth-connections/list)
24-
- [`/dev-orgs.auth-connections.update`](/beta/api-reference/dev-orgs/auth-connections/update)
25-
26-
### Incident Support
27-
Added incident type support across multiple endpoints:
28-
29-
#### Timeline and Conversation Endpoints
30-
Added `incident` to supported object types in:
31-
- [`/conversations.create`](/beta/api-reference/conversations/create)
32-
- [`/conversations.export`](/beta/api-reference/conversations/export)
33-
- [`/conversations.get`](/beta/api-reference/conversations/get)
34-
- [`/conversations.list`](/beta/api-reference/conversations/list)
35-
- [`/conversations.update`](/beta/api-reference/conversations/update)
36-
- [`/timeline-entries.create`](/beta/api-reference/timeline-entries/create)
37-
- [`/timeline-entries.get`](/beta/api-reference/timeline-entries/get)
38-
- [`/timeline-entries.list`](/beta/api-reference/timeline-entries/list)
39-
- [`/timeline-entries.update`](/beta/api-reference/timeline-entries/update)
40-
41-
#### Search Endpoints
42-
Added incident support to search results in:
43-
- [`/search.core`](/beta/api-reference/search/core)
44-
- [`/search.hybrid`](/beta/api-reference/search/hybrid)
45-
46-
#### Links and Schema Endpoints
47-
Added incident type to object references in:
48-
- [`/links.create`](/beta/api-reference/links/create)
49-
- [`/links.get`](/beta/api-reference/links/get)
50-
- [`/links.list`](/beta/api-reference/links/list)
51-
- [`/schemas.stock.get`](/beta/api-reference/schemas/stock/get)
52-
- [`/schemas.stock.list`](/beta/api-reference/schemas/stock/list)
53-
54-
#### Webhook Events
55-
Added new incident event types:
56-
- `incident_created`
57-
- `incident_deleted`
58-
- `incident_updated`
59-
60-
These events are available in:
61-
- [`/webhooks.create`](/beta/api-reference/webhooks/create)
62-
- [`/webhooks.get`](/beta/api-reference/webhooks/get)
63-
- [`/webhooks.list`](/beta/api-reference/webhooks/list)
64-
- [`/webhooks.update`](/beta/api-reference/webhooks/update)
65-
66-
### Work Updates
67-
Added sync resolution fields to `staged_info` in:
68-
- [`/works.update`](/beta/api-reference/works/update)
69-
- Added `sync_in_unresolved_fields`
70-
- Added `sync_out_unresolved_fields`
71-
- Removed `unresolved_fields`
4+
### Dev Users
5+
- `POST /dev-users.activate` - New endpoint
6+
- `POST /dev-users.deactivate` - New endpoint
7+
8+
## Modified Endpoints
9+
### Articles
10+
- Modified description for `scope` parameter in:
11+
- `GET /articles.count`
12+
- `POST /articles.count`
13+
- `GET /articles.list`
14+
- `POST /articles.list`
15+
- Description changed to: "Filter for the scope of the articles."
16+
17+
### Parts
18+
- Added `custom_schema_spec` property to request body in:
19+
- `POST /parts.create`
20+
- `POST /parts.update`
21+
22+
### Works
23+
- Modified `staged_info` in `POST /works.update`:
24+
- Removed required property: `unresolved_fields`
25+
- Added new properties:
26+
- `sync_in_unresolved_fields`
27+
- `sync_out_unresolved_fields`
28+
29+
### Auth Connections
30+
- Deprecated Azure AD and Google Apps auth connection options in:
31+
- `POST /dev-orgs.auth-connections.create`
32+
- `GET /dev-orgs.auth-connections.get`
33+
- `POST /dev-orgs.auth-connections.get`
34+
- `GET /dev-orgs.auth-connections.list`
35+
- `POST /dev-orgs.auth-connections.list`
36+
- `POST /dev-orgs.auth-connections.update`
37+
38+
### Webhooks
39+
- Added new event types (`incident_created`, `incident_deleted`, `incident_updated`) to:
40+
- `POST /webhooks.create`
41+
- `GET /webhooks.get`
42+
- `POST /webhooks.get`
43+
- `GET /webhooks.list`
44+
- `POST /webhooks.list`
45+
- `POST /webhooks.update`
46+
47+
## Schema Changes
48+
Added support for incident type across multiple schemas affecting:
49+
- Conversations endpoints
50+
- Links endpoints
51+
- Timeline entries endpoints
52+
- Search endpoints
53+
- Schemas stock endpoints
54+
55+
The incident type was added to object types, event types, and reference types in these endpoints' response schemas.

0 commit comments

Comments
 (0)