[AutoPR sdk-messaging/eventgrid/azsystemevents]-generated-from-SDK Generation - Go-6132552

[Azure SDK Bot (azure-sdk)]

Configurations: 'specification/eventgrid/data-plane/EventGridSystemEvents/tspconfig.yaml', API Version: 2024-01-01, SDK Release Type: beta, and CommitSHA: '964e827a2beb3838001819532f1bafac405c520f' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6132552 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

sdk/messaging/eventgrid/azsystemevents

[Judy Liu (jliusan)]

Copilot please fix CI failure

[Judy Liu (jliusan)]

Copilot resolve the merge conflicts in this pull request

[Copilot]

Copilot please fix CI failure

Fixed in commit b36eac7. I restored sdk/messaging/eventgrid/azsystemevents/time_rfc3339.go, which was missing and causing compile failures (populateDateTimeRFC3339/unpopulateDateTimeRFC3339 undefined). I also verified with go test ./... in the module.

[Copilot]

Copilot resolve the merge conflicts in this pull request

Resolved merge conflicts in commit 9706ca7. I accepted the main branch changes for:

• models.go: Updated field naming (ToBsuid/FromBsuid per new emitter conventions)
• models_serde.go: Updated serialization code using generic time helpers
• testdata/_metadata.json: Emitter version 0.11.0
• tsp-location.yaml: Spec commit 7089f3d2

Tests pass successfully.

[Judy Liu (jliusan)]

Copilot fix ci failure

[Copilot]

Copilot fix ci failure

Fixed in commit 4e9b1e5. The CI analyze job was failing because the required doc.go file was missing from the azsystemevents module. I've added the file with appropriate package documentation.

[Judy Liu (jliusan)]

Copilot revert to this commit:605c4a2a8b5867d3aac9e9b2d7267d8ac35de946

[Copilot]

Copilot revert to this commit:605c4a2a8b5867d3aac9e9b2d7267d8ac35de946

To revert to commit 605c4a2, I need to force-push the branch, which requires special permissions.

As an alternative, I can create a new commit that reverts all my previous changes (restoring time_rfc3339.go removal, undoing merge conflict resolution, and removing doc.go). This would achieve the same end state as commit 605c4a2 without requiring a force push.

Would you like me to proceed with the revert commit approach, or would you prefer to handle the force-push to 605c4a2 manually?

[github-actions]

Hi Azure SDK Bot (@azure-sdk). Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi Azure SDK Bot (@azure-sdk). Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.