Explore richer Git provider integrations for deployments
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- github, typescript
- Domain
- backend, developer-experience, devops
Research direction
Start by reading the existing Git provider integrations and Issue #2712, especially the GitHub Preview Deployment comment flow. Map where deployment status, URL, and log links could be added for commits, pull requests, and merge requests. Done means agreeing on the providers, workflows, and concrete integration scope before implementation.
Written by the indexing model from the issue text.
Description
What problem will this feature address?
Dokploy connects to Git providers to deploy changes, but deployment tracking happens primarily in Dokploy. A richer connection could save developers from switching tools to check the status of a deployment linked to their commit or pull request.
Describe the solution you'd like
Explore ways to make Git provider integrations more useful throughout the deployment lifecycle. For example, Dokploy could surface deployment status, the deployed URL, or links to logs from the related commit, pull request, or merge request.
These are starting points rather than fixed requirements. Would this broader integration be useful? Which providers and workflows would benefit most?
Describe alternatives you've considered
Users can check the deployment in Dokploy and share its status or URL manually. GitHub Preview Deployment comments already cover part of this workflow.
Additional context
This is an exploratory feature request; the goal is to get feedback on whether richer Git provider integrations would be valuable. Issue #2712 is related, but focuses on custom comment text for webhook-triggered deployments.
Will you send a PR to implement it?
Yes
- Dominant language
- TypeScript
- Stars
- 38.2k
- Forks
- 3.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 69
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Dokploy/dokploy
-
needs-triage🔍
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Dokploy/dokploy#5836 · 1 comment ·
Maintainers usually reply within 1 day
-
Server threshold (CPU/Memory) alerts for the main Dokploy server never reach any notificationPossibly taken @ghazy2001 claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Dokploy/dokploy#5830 · 1 comment ·
Maintainers usually reply within 1 day
-
Add a "System" option to the dark/light mode setting (follow OS appearance)Possibly taken @fabianfrankwerner claimed this 25 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Dokploy/dokploy#5638 · 1 comment ·
Maintainers usually reply within 1 day
-
compose.search omits services missing from member accessedServices, even for owners/adminsPossibly taken @imrja8 claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Dokploy/dokploy#5361 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
[Feature Request] Show usage example for File Mounts created in the UIPossibly taken @jereok91 claimed this 47 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Dokploy/dokploy#5147 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
area: frontend priority: normal
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
formbricks/formbricks#9918 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
thecodacus/pithagoras#364 ·
Maintainers usually reply within 1 day
-
TestAutonomousStop_ReportsObservedState fails under host load: 1s wall-clock ceiling vs 250ms cycleOpentype:bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nightgauge/nightgauge#2909 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day