Skip to content

Open Source the Wiki required for contributing to API Specifications #7315

@tombuildsstuff

Description

@tombuildsstuff

👋

Honestly I'm not sure where I should be making this feature request - but here we are.

Occasionally during PR Review the Wiki in this repository is linked too to provide more contextual information about why specific validation failures happen - however unfortunately it's Private:

Whilst the bulk of the changes in this repository are sent by Microsoft Employees - third-parties also contribute to this repository to fix issues where the API Response doesn't match the API Definition (for example #6917 and #7246) - as such the Specifications for the API Specifications (for want of a better word 😄) are frequently linked to in PR's (for example #7246 (comment)) - and thus I believe the contents of that Wiki appear to be required to be able to effectively contribute to this repository.

Since this information isn't available, third-party PR's often fall by the way-side, since the build is broken with no means of determining why (for example #6917, #7246, #2880, #2645 and #757) - which leads to wasted effort on both third-parties (sending the PR) and Microsoft's front (having to review it, and then close said PR's) - meaning the API Specification remains outdated.

As it appears the contents of this Wiki are required to being able to contribute to this repository - would it be possible for this Wiki to be open-sourced?

It's worth noting this is also linked to in the readme which this issue's tracking: #4770 - so other users have noticed the same issue, but not raised an issue about it

Thanks!

Metadata

Metadata

Assignees

Labels

customer-reportedIssues that are reported by GitHub users external to the Azure organization.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions