Use $GITHUB_EVENT_PATH variable instead of inline file writing #9134
Conversation
benbp
added
the
Central-EngSys
|
The following pipelines have been queued for testing: |
|
The following pipelines have been queued for testing: |
benbp
force-pushed
the
benbp/gh-event-logging
branch
from
fb9ab78 to
692203f
Compare
|
The following pipelines have been queued for testing: |
…1412) Sync .github/workflows directory with azure-sdk-tools for PR Azure/azure-sdk-tools#9134 See [eng/common workflow](https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/README.md#workflow) --------- Co-authored-by: Ben Broderick Phillips <[email protected]>
| ${{ toJson(github.event) }} | ||
| EOF | ||
| github-event-processor ${{ github.event_name }} payload.json CloseAddressedIssues | ||
| github-event-processor ${{ github.event_name }} ${{ github.event_path }} |
There was a problem hiding this comment.
Looks like we all missed the fact you deleted CloseAddressedIssues which is causing failures like https://github.com/Azure/azure-sdk/actions/runs/11358965282/job/31594328835
5 participants
Reduce github event processor logging
FYI @JimSuplizio I didn't know until now that you can grab the webhook payload from disk (thanks to @hallipr). This saves us a lot of log storage space, as before I was putting the whole payload inline to the bash command (to work around env var max size issues).