Remove sections

Author: ehmicky

src/convert.test.js.md

@@ -11835,65 +11835,6 @@ Generated by [AVA](https://ava.li).
       },
       swagger: '2.0',
       tags: [
-        {
-          description: `All URLs start with `https://api.netlify.com/api/v1/`. SSL only. The path is prefixed with the API version. If we change the API in backward-incompatible ways, we’ll bump the version marker and maintain stable support for the old URLs.␊
-          ␊
-          To make a request for all the sites you have access to, you’d append the sites’ index path to the base URL to form something like `https://api.netlify.com/api/v1/sites`. In curl, that looks like:␊
-          ```http␊
-            curl -H 'User-Agent: MyApp ([email protected])'␊
-            https://api.netlify.com/api/v1/sites?access_token=oauth2_access_token␊
-          ````,
-          name: 'Making a request',
-          'x-traitTag': true,
-        },
-        {
-          description: `Netlify uses OAuth2 for authentication. All requests must use HTTPS. You’ll need an application client key and a client secret before you can access the Netlify API. You can register a new application at https://app.netlify.com/applications.␊
-          ␊
-          If you’re making a public integration with Netlify for others to enjoy, you must use OAuth 2. This allows users to authorize your application to use Netlify on their behalf without having to copy/paste API tokens or touch sensitive login info.␊
-          ␊
-          The OAuth2 end-user authorization endpoint is `https://app.netlify.com/authorize`.`,
-          name: 'Authenticating',
-          'x-traitTag': true,
-        },
-        {
-          description: `To protect Netlify from getting flooded by automated deploys or misbehaving applications, the Netlify API is rate limited.␊
-          ␊
-          You can make up to 200 requests per minute.␊
-          ␊
-          You can check the returned HTTP headers of any API request to see your current rate limit status:␊
-          ```http␊
-            X-RateLimit-Limit: 200␊
-            X-RateLimit-Remaining: 56␊
-            X-RateLimit-Reset: 1372700873␊
-          ```␊
-          If you need higher limits, please [contact us](https://www.netlify.com/support).`,
-          name: 'Rate limiting',
-          'x-traitTag': true,
-        },
-        {
-          description: `Requests that return multiple items will be paginated to 100 items by default. You can specify further pages with the `?page` parameter. You can also set a custom page size up to 100 with the `?per_page` parameter.␊
-          ␊
-          Note that page numbering is 1-based and that omitting the `?page` parameter will return the first page.␊
-          ### Link header␊
-          The pagination info is included in the `Link` header.␊
-          ```http␊
-            Link: <https://api.netlify.com/api/v1/sites?page=3&per_page=20>; rel="next",␊
-            <https://api.netlify.com/api/v1/sites?page=5&per_page=20>; rel="last"␊
-          ```␊
-          Linebreak is included for readability.␊
-          ␊
-          The possible `rel` values are:␊
-          - `next` Shows the URL of the immediate next page of results.␊
-          - `last` Shows the URL of the last page of results.␊
-          - `prev` Shows the URL of the immediate previous page of results.`,
-          name: 'Pagination',
-          'x-traitTag': true,
-        },
-        {
-          description: 'Whenever the API requires a `{site_id}`, you can either use the UUID of a site obtained through the API, or the domain of the site (`mysite.netlify.com`/`www.example.com`). These two are interchangeable whenever they’re used in API paths.',
-          name: 'Site IDs',
-          'x-traitTag': true,
-        },
         {
           name: 'ticket',
           'x-displayName': 'Ticket',
@@ -12016,16 +11957,6 @@ Generated by [AVA](https://ava.li).
         },
       ],
       'x-tagGroups': [
-        {
-          name: 'General',
-          tags: [
-            'Making a request',
-            'Authenticating',
-            'Rate limiting',
-            'Pagination',
-            'Site IDs',
-          ],
-        },
         {
           name: 'OAuth',
           tags: [

src/convert.test.js.snap

@@ -2477,13 +2477,6 @@ definitions:
         type: string
         x-nullable: false
 x-tagGroups:
-  - name: General
-    tags:
-      - Making a request
-      - Authenticating
-      - Rate limiting
-      - Pagination
-      - Site IDs
   - name: OAuth
     tags:
       - ticket
@@ -2539,78 +2532,6 @@ x-tagGroups:
       - asset
       - assetPublicSignature
 tags:
-  - name: Making a request
-    description: >-
-      All URLs start with `https://api.netlify.com/api/v1/`. SSL only. The path is prefixed with the API version. If we change the API in backward-incompatible ways, we’ll bump the version marker and maintain stable support for the old URLs.
-
-
-      To make a request for all the sites you have access to, you’d append the sites’ index path to the base URL to form something like `https://api.netlify.com/api/v1/sites`. In curl, that looks like:
-
-      ```http
-        curl -H 'User-Agent: MyApp ([email protected])'
-        https://api.netlify.com/api/v1/sites?access_token=oauth2_access_token
-      ```
-
-    x-traitTag: true
-  - name: Authenticating
-    description: >-
-      Netlify uses OAuth2 for authentication. All requests must use HTTPS. You’ll need an application client key and a client secret before you can access the Netlify API. You can register a new application at https://app.netlify.com/applications.
-
-
-      If you’re making a public integration with Netlify for others to enjoy, you must use OAuth 2. This allows users to authorize your application to use Netlify on their behalf without having to copy/paste API tokens or touch sensitive login info.
-
-
-      The OAuth2 end-user authorization endpoint is `https://app.netlify.com/authorize`.
-    x-traitTag: true
-  - name: Rate limiting
-    description: >-
-      To protect Netlify from getting flooded by automated deploys or misbehaving applications, the Netlify API is rate limited.
-
-
-      You can make up to 200 requests per minute.
-
-
-      You can check the returned HTTP headers of any API request to see your current rate limit status:
-
-      ```http
-        X-RateLimit-Limit: 200
-        X-RateLimit-Remaining: 56
-        X-RateLimit-Reset: 1372700873
-      ```
-
-      If you need higher limits, please [contact us](https://www.netlify.com/support).
-    x-traitTag: true
-  - name: Pagination
-    description: >-
-      Requests that return multiple items will be paginated to 100 items by default. You can specify further pages with the `?page` parameter. You can also set a custom page size up to 100 with the `?per_page` parameter.
-
-
-      Note that page numbering is 1-based and that omitting the `?page` parameter will return the first page.
-
-      ### Link header
-
-      The pagination info is included in the `Link` header.
-
-      ```http
-        Link: <https://api.netlify.com/api/v1/sites?page=3&per_page=20>; rel="next",
-        <https://api.netlify.com/api/v1/sites?page=5&per_page=20>; rel="last"
-      ```
-
-      Linebreak is included for readability.
-
-
-      The possible `rel` values are:
-
-      - `next` Shows the URL of the immediate next page of results.
-
-      - `last` Shows the URL of the last page of results.
-
-      - `prev` Shows the URL of the immediate previous page of results.
-    x-traitTag: true
-  - name: Site IDs
-    description: >-
-      Whenever the API requires a `{site_id}`, you can either use the UUID of a site obtained through the API, or the domain of the site (`mysite.netlify.com`/`www.example.com`). These two are interchangeable whenever they’re used in API paths.
-    x-traitTag: true
   - name: ticket
     x-displayName: Ticket
   - name: accessToken