Update Azure Typespec documentation with current Azure SDK processes.
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 115
Description
Where Azure TypeSpec docs mention our team’s process, replace restated steps with links to the corresponding EngHub pages. This keeps Docs, the bot, and teams aligned to a single source of truth.
See this as an example of when the bot got the answer wrong because the documentation is wrong:
- Question in [TypeSpec Testing channel](https://teams.microsoft.com/l/message/19:rMhMrxg7UjfwZmVoSeVvWvNQIfT_G6ds8napsytWqzw1@thread.tacv2/1763165434971?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=39910aef-85da-4e30-b5e3-35f04ef38648&parentMessageId=1763165434971&teamName=Azure%20SDK%20Q%26A%20Bot%20Testing&channelName=Azure%20SDK%20QA%20bot%20for%20TypeSpec%20Testing&createdTime=1763165434971)
Contributor guide
Research direction
Start by locating the Azure TypeSpec documentation sections that describe team processes, then compare each restated step with the corresponding current EngHub page. Replace process descriptions with links to the single source of truth and verify the affected docs address the TypeSpec Testing example without retaining outdated guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100