Git Provider Deployment: no deploy info override on automatic deployments
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Deployment metadata extracted in webhook handlers currently seem to get overriden by changes implemented in https://github.com/Dokploy/dokploy/pull/3018.
This could reduce traceability of deployments in case the trigger didn't match the latest commit in the linked repository (e.g. GitHub: compose deployment triggered by registry_package).
Describe the solution you'd like
Deployment metadata received from autodeploy pipelines should not be overridden.
The deployment info should only be patched for manual deployments.
Describe alternatives you've considered
Additional context
No response
Will you send a PR to implement it?
No
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 reviewing the webhook handlers and the changes introduced in PR #3018. Trace how deployment metadata is handled for automatic versus manual deployments, then verify that automatic deployment metadata remains unchanged while manual deployment information can still be patched.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100