argoproj / argoproj/notifications-engine
Support `payload` field on GitHub Deployment notifications
- Dominant language
- Go
- Stars
- 334
- Forks
- 217
- PR merge metrics
- No merged PRs in 30d
Description
When creating a deployment with the Github integration, I would like to be able to pass `payload` into the deployment.
As per the [Github docs](https://docs.github.com/en/rest/deployments/deployments?apiVersion=2026-03-10#create-a-deployment):
```
The payload parameter is available for any extra information that a deployment system might need. It is a JSON text field that will be passed on when a deployment event is dispatched.
```
Would a PR that adds `payload` as a parameter that can be passed in from the argocd trigger be considered and accepted?
If so, I will open one.
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests; start by tracing the GitHub integration's deployment creation path and how parameters from the Argo CD trigger are handled. Confirm the existing deployment fields and GitHub API request, then verify that a supplied JSON payload is accepted and forwarded with the deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100