-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include notification for new directory structure #1364
Conversation
Adding description to the new upcoming changes to the repos folder structure
Could you please take a look at the comments in #1360 and address them here? Not sure why that PR got closed and new one was opened ... |
Fixed the structure
updated Tag values to "package-2017-03" I hope this is what you meant cause honestly I don't have a lot of context on the decision or pattern for this value :)
Captain @kirthik Your comments have been addressed in my latest commits, please let me know if there's more to be changed here Thanks and God Speed LOL |
README.md
Outdated
|
||
```bash | ||
. | ||
├──automation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure whether we intentionally skipped the top node specification
or not https://github.com/Azure/azure-rest-api-specs/tree/reorg. Other than that LGTM! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmmm, good point let me add it
Added root folder "Specification"
No modification for AutorestCI/azure-sdk-for-python |
No modification for AutorestCI/azure-sdk-for-ruby |
No modification for AutorestCI/azure-sdk-for-node |
Adding description to the new upcoming changes to the repos folder structure
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
api-version
in the path should match theapi-version
in the spec).Quality of Swagger