Repository navigation
Hashtag in branch name not supported #4585
Description
To Reproduce
- Setup Gitlab Provider
- Create a new application
- Select Gitlab Provider
- Select repository
- Select branch with a hashtag
#in the name - Save the configuration
Current vs. Expected behavior
Branchname with a hashtag are not supported:
Without the hashtag:
Provide environment information
Dokploy Version: v0.29.8Which area(s) are affected? (Select all that apply)
Application
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
No response
Will you send a PR to fix it?
No
Activity
dosubot commentedon Jun 9, 2026
Hi @GeiOoo! I'm Dosu and I'm helping the Dokploy team.
I can confirm this is a real bug. Branch names are interpolated directly into git clone commands without any shell escaping or URL encoding [1]:
The
#character is problematic because in shell contexts it starts a comment, which would truncate the command. It also acts as a fragment identifier in URLs, breaking any API calls that include the branch name in the URL path.This affects all Git providers (GitHub, GitLab, Bitbucket, Gitea, custom Git) since they all follow the same pattern of directly inserting the branch name into the command string without quoting [2] [3] [4] [5].
A fix would involve properly quoting the branch name in shell commands (e.g., wrapping
${gitlabBranch}in double quotes like"${gitlabBranch}") and applyingencodeURIComponent()where branch names appear in URLs.To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
fix(validation): allow hashtag in git branch names (Dokploy#4714)
chore(release): 0.37.0 [skip ci]