# Bug OP-16766 - GitHub and GitLab extensions branch name generation might generate problematic branch names

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-16766

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 15.5.0 |
| Observed in versions |  |
| Sprint | 15.5.0 |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Klaus Zanders |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Create a work package in a project that has the gitlab or github module enabled
    
2.  Give it a name that contains a comma
    
3.  Go to the work package page
    
4.  Go to the GitHub/GitLab tab
    
5.  Click on &quot;Git Snippets&quot;
    
6.  Look at the &quot;Name of the Branch&quot;
    

### What is the buggy behavior?

*   The branch name contains the comma from the WP title. This will trip up some external tools like the Git command line client or our own CI
    

### What is the expected behavior?

1.  The branch name should only contain latin ascii characters (a-z, A-Z, 0-9) and `-`, `_` and `/` as special characters
