# Code support on commit messages

**URL:** <https://forum.buildkite.community/t/code-support-on-commit-messages/1100>\
**Category:** Features Requests\
**Created:** [June 8, 2020, 6:14pm UTC](https://forum.buildkite.community/t/code-support-on-commit-messages/1100 "2020-06-08T18:14:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gencer](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/gencer/32/647_2.png) [@gencer](https://forum.buildkite.community/u/gencer)\
**Post date:** [June 8, 2020, 6:14pm UTC](https://forum.buildkite.community/t/code-support-on-commit-messages/1100/1 "2020-06-08T18:14:19Z")

</div>

Hi folks,

Can we convert backticks to `<code> **CODE** </code>` on Buildkite’s pipeline commit message? Let me illustrate:

 ![SNAG-0291](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/1X/b93017e575fe23892f653dd23b458122f468d5db.png)

This is just a simple `<code>`. This can be a different font like bold or color. To make sure it is a partial code.

Can this be added?

Thanks,  
Gencer.

---

<div class="post-metadata">

**Author:** ![anon57234190](https://avatars.discourse-cdn.com/v4/letter/a/a88e4f/32.png) [@anon57234190](https://forum.buildkite.community/u/anon57234190)\
**Post date:** [July 27, 2020, 4:31am UTC](https://forum.buildkite.community/t/code-support-on-commit-messages/1100/2 "2020-07-27T04:31:49Z")

</div>

Hi Gencer,

Thanks for this! We’ve had a look at it and we’re a bit hesitant to apply any formatting to this particular section. The reason for this is that these are generally commit messages—GitHub doesn’t employ any markdown flavoured formatting (including backticks!) to it on their end.

Cheers,  
Eleanor

---

<div class="post-metadata">

**Author:** ![gencer](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/gencer/32/647_2.png) [@gencer](https://forum.buildkite.community/u/gencer)\
**Post date:** [August 3, 2020, 3:58am UTC](https://forum.buildkite.community/t/code-support-on-commit-messages/1100/3 "2020-08-03T03:58:03Z")

</div>

Hi Eleanor,

Thank you for taking this in consideration.

I understand your hesitation on this.

Thanks,  
Gencer.

---

<div class="post-metadata">

**Author:** ![gencer](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/gencer/32/647_2.png) [@gencer](https://forum.buildkite.community/u/gencer)\
**Post date:** [May 23, 2021, 7:59am UTC](https://forum.buildkite.community/t/code-support-on-commit-messages/1100/4 "2021-05-23T07:59:53Z")

</div>

> GitHub doesn’t employ any markdown flavoured formatting (including backticks!) to it on their end.

And they are doing it now. GitHub supports code blocks in commit messages, issues, PRs and everywhere. Can we revisit this?

See: [Back-tick code blocks are now supported in titles | GitHub Changelog](https://github.blog/changelog/2021-04-13-back-tick-code-blocks-are-now-supported-in-titles/)