Skip to content

Reverting recovery services specs to fix docs builds#1074

Merged
dsgouda merged 1 commit into
Azure:masterfrom
dsgouda:recov
Mar 27, 2017
Merged

Reverting recovery services specs to fix docs builds#1074
dsgouda merged 1 commit into
Azure:masterfrom
dsgouda:recov

Conversation

@dsgouda
Copy link
Copy Markdown
Contributor

@dsgouda dsgouda commented Mar 27, 2017

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

  • I have read the contribution guidelines.
  • My spec meets the review criteria:
    • The spec conforms to the Swagger 2.0 specification.
    • Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
    • The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

Cross references in recovery services specs is causing build failures for docs team since they don't support it yet. Reverting changes introduced here
These changes will be re-introduced once the docs teams add support for cross referencing in swagger specs

Copy link
Copy Markdown
Member

@salameer salameer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved on reverting the change

Copy link
Copy Markdown
Contributor

@vishrutshah vishrutshah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Just minor & non-blocker you should have used git revert so that you don't need to supply message.

@dsgouda dsgouda merged commit ddaf1b1 into Azure:master Mar 27, 2017
@AutorestCI
Copy link
Copy Markdown

No modification for Python

@AutorestCI
Copy link
Copy Markdown

No modification for NodeJS

@AutorestCI
Copy link
Copy Markdown

dsgouda added a commit to dsgouda/azure-rest-api-specs that referenced this pull request Mar 30, 2017
@AutorestCI
Copy link
Copy Markdown

No modification for NodeJS

@AutorestCI
Copy link
Copy Markdown

No modification for Python

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants