Feature #24065
closedCommit message shouldn't be rendered by Markdown or Textile
0%
Description
Hello, our team is using Redmine 3.30 and git as VCS.
GitExtension is the default git client.
Recently, we changed our project text formatting from Textile to Markdown, the problem happened:
The commit message in 'Repository' will rendered as Markdown format as well.
---
Reason:
When merging a branch in GitExtension, it will automatically generating a commit message like the following:
# Conflicts: # path/to/conflict/file # path/to/conflict/file # path/to/conflict/file
Compared with some other website(such as GitHub, Gitlab etc...)
They didn't treat these commit message as Markdown, just raw plain text.
Environment:
Redmine version 3.3.0.stable
Ruby version 2.2.5-p319 (2016-04-26) [x86_64-linux]
Rails version 4.2.6
Environment production
Database adapter Mysql2
SCM:
Subversion 1.8.10
Mercurial 3.1.2
Bazaar 2.7.0
Git 2.1.4
Filesystem
Redmine plugins:
no plugin installed
Files
Related issues
Updated by Toshi MARUYAMA almost 8 years ago
- Tracker changed from Defect to Feature
Updated by Toshi MARUYAMA almost 8 years ago
- Subject changed from Commit message shouldn't be rendered by Markdown to Commit message shouldn't be rendered by Markdown or Textile
Updated by Toshi MARUYAMA almost 8 years ago
- Category changed from Text formatting to SCM
Updated by Toshi MARUYAMA over 7 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Updated by Toshi MARUYAMA over 7 years ago
- Related to Feature #22758: Make text formatting of commit messages optional added