Merge branch 'segmentio:main' into feature/updates

Author: GoodmanBen

.github/workflows/label-prs.yml

@@ -60,3 +60,46 @@ jobs:
               });
               await Promise.all(requests);
             }
+
+      - name: Comment for mapping-kit changes
+        uses: actions/github-script@v7
+        env:
+          labelsToAdd: '${{ steps.compute-labels.outputs.add }}'
+          labelsToRemove: '${{ steps.compute-labels.outputs.remove }}'
+        with:
+          script: |
+            const { labelsToAdd, labelsToRemove, DRY_RUN } = process.env
+            const shouldAddComment = labelsToAdd.length > 0 && labelsToAdd.split(",").some(x=>x.includes("mappingkit"))
+            const shouldRemoveComment = labelsToRemove.length > 0 && labelsToRemove.split(",").some(x=>x.includes("mappingkit"))
+            // Get the list of comments on the PR
+            const response = await github.rest.issues.listComments({
+                issue_number: context.issue.number,
+                owner: context.repo.owner,
+                repo: context.repo.repo
+            })
+            const mappingKitComment = response.data.find(comment => comment.body.includes('mapping-kit go'))
+            if(shouldAddComment){
+                if (mappingKitComment) {
+                  console.log('Already commented on this PR')
+                  return
+                }
+                // Add comment to the PR
+                await github.rest.issues.createComment({
+                    issue_number: context.issue.number,
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    body: `This PR makes changes to mapping-kit. Please ensure that the changes are reflected in the [mapping-kit go](https://github.com/segmentio/mapping-kit) library as well and link the PR in description.`
+                  })
+            }
+            if(shouldRemoveComment) {
+              if (!mappingKitComment) {
+                console.log('No mapping-kit comment to remove')
+                return
+              }
+              // Remove comment from the PR
+              await github.rest.issues.deleteComment({
+                  comment_id: mappingKitComment.id,
+                  owner: context.repo.owner,
+                  repo: context.repo.repo
+                })
+            }

README.md

@@ -31,6 +31,7 @@ For more detailed instruction, see the following READMEs:
 - [Presets](#presets)
 - [perform function](#the-perform-function)
 - [Batching Requests](#batching-requests)
+- [Parsing MultiStatus Responses](#parsing-multistatus-responses)
 - [Action Hooks](#action-hooks)
 - [HTTP Requests](#http-requests)
 - [Support](#support)
@@ -736,6 +737,12 @@ Keep in mind a few important things about how batching works:
 
 Additionally, you’ll need to coordinate with Segment’s R&D team for the time being. Please reach out to us in your dedicated Slack channel!
 
+## Parsing MultiStatus Responses
+
+When a batch request to a destination returns a 207 MultiStatus response, the `performBatch` method will typically receive an array of responses, indicating the status of each event in the batch. The Actions Framework provides a `MultiStatusResponse` class to help you parse these responses to report a more granular success or failure status for each event.
+
+A detailed example of how to use the `MultiStatusResponse` class can be found in the [MultiStatus Documentation](./docs/multistatus.md).
+
 ## Action Hooks
 
 Hooks allow builders to perform requests against a destination at certain points in the lifecycle of a mapping. Values can then be persisted from that request to be used later on in the action's `perform` method.