Dokploy / Dokploy/dokploy

Preview Deployment not deployed correctly in Pull Request from forked repository

Open
#1,673 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

To Reproduce
  1. Create application
  2. Enable Preview Deployment
  3. Create a Pull Request from one of the forked repository
  4. Visit /etc/dokploy/applications/{{aplication_name_preview}}/code in host machine
  5. Execute git ls-remote --get-url origin

When you follow the steps, in the preview code folder, the remote origin url is not the pull request source repository, but it is the application's repository

Current vs. Expected behavior

Following the steps

Expected Behaviour:
When accessing the preview deployment folder (/dokploy/applications/{{application_name_preview}}/code) on the host machine, the repository should reflect the source repository with the pull request (PR).

Current Behavior:
Instead of being on the pull request source repository, the repository remains on the application's repository. This prevents the preview deployment from accurately reflecting the PR changes.

Provide environment information
Operating System:
  OS: Debian GNU/Linux 12 (bookworm)
  Arch: x86_64
Dokploy version: v0.21.5
VPS Provider: Hostinger

In Nextjs static export with nixpacks
Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Remote server

Additional context

No response

Will you send a PR to fix it?

Maybe, need help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Reproduce the forked pull request preview deployment, then trace how the preview repository is configured and verify the resulting code directory's origin; done means it points to the pull request source repository while normal application deployments remain unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.