fix(specs): tag for push (#5029) (generated) [skip ci]

Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>

Author: algolia-bot

docs/bundled/ingestion.json

@@ -231,7 +231,10 @@
     },
     "/1/push/{indexName}": {
       "post": {
-        "summary": "Pushes records to be transformed through the Pipeline, directly to an index",
+        "tags": [
+          "tasks"
+        ],
+        "summary": "Pushes records to be transformed through the Pipeline, by indexName",
         "description": "Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task.\nIf you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records.\nThis method is similar to `pushTask`, but requires an `indexName` instead of a `taskID`. If zero or many tasks are found, an error will be returned.\n",
         "operationId": "push",
         "x-acl": [
@@ -1576,7 +1579,7 @@
         "tags": [
           "tasks"
         ],
-        "summary": "Pushes records to be transformed through the Pipeline, directly to an index",
+        "summary": "Pushes records to be transformed through the Pipeline, by taskID",
         "description": "Pushes records through the Pipeline, directly to an index. You can make the call synchronous by providing the `watch` parameter, for asynchronous calls, you can use the observability endpoints and/or debugger dashboard to see the status of your task.\nIf you want to leverage the [pre-indexing data transformation](https://www.algolia.com/doc/guides/sending-and-managing-data/send-and-update-your-data/how-to/transform-your-data/), this is the recommended way of ingesting your records.\nThis method is similar to `push`, but requires a `taskID` instead of a `indexName`, which is useful when many `destinations` target the same `indexName`.\n",
         "operationId": "pushTask",
         "x-acl": [

docs/bundled/ingestion.yml

@@ -1029,9 +1029,9 @@ paths:
             // >LOG
   /1/push/{indexName}:
     post:
-      summary: >-
-        Pushes records to be transformed through the Pipeline, directly to an
-        index
+      tags:
+        - tasks
+      summary: Pushes records to be transformed through the Pipeline, by indexName
       description: >
         Pushes records through the Pipeline, directly to an index. You can make
         the call synchronous by providing the `watch` parameter, for
@@ -9179,9 +9179,7 @@ paths:
     post:
       tags:
         - tasks
-      summary: >-
-        Pushes records to be transformed through the Pipeline, directly to an
-        index
+      summary: Pushes records to be transformed through the Pipeline, by taskID
       description: >
         Pushes records through the Pipeline, directly to an index. You can make
         the call synchronous by providing the `watch` parameter, for

specs/bundled/ingestion.yml

@@ -231,9 +231,9 @@ paths:
         - ingestion
   /1/push/{indexName}:
     post:
-      summary: >-
-        Pushes records to be transformed through the Pipeline, directly to an
-        index
+      tags:
+        - ingestion
+      summary: Pushes records to be transformed through the Pipeline, by indexName
       description: >
         Pushes records through the Pipeline, directly to an index. You can make
         the call synchronous by providing the `watch` parameter, for
@@ -283,8 +283,6 @@ paths:
                 $ref: '#/components/schemas/WatchResponse'
         '400':
           $ref: '#/components/responses/BadRequest'
-      tags:
-        - ingestion
   /1/authentications:
     get:
       tags:
@@ -1113,9 +1111,7 @@ paths:
     post:
       tags:
         - ingestion
-      summary: >-
-        Pushes records to be transformed through the Pipeline, directly to an
-        index
+      summary: Pushes records to be transformed through the Pipeline, by taskID
       description: >
         Pushes records through the Pipeline, directly to an index. You can make
         the call synchronous by providing the `watch` parameter, for