Description of deployment in webhook or API
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
When I deploy by webhook it ignores the text parameter and always shows: "NEW CHANGES"
Describe the solution you'd like
Parameter in webhook or API to change this message so I can put the commit message for example (I have my own GitHub Action that triggers the deployment).
Describe alternatives you've considered
None
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the webhook and API deployment entry points to where the "NEW CHANGES" message is set. Check how deployment parameters are passed, and consider the existing deployment flow and GitHub Action context; the work is done when an explicit parameter can replace the default message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100