# Custom GitHub status name **URL:** \ **Category:** General\ **Created:** [February 6, 2021, 7:04pm UTC](https://forum.buildkite.community/t/custom-github-status-name/1447 "2021-02-06T19:04:18Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![ngan](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ngan/32/662_2.png) [@ngan](https://forum.buildkite.community/u/ngan)\ **Post date:** [February 6, 2021, 7:04pm UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/1 "2021-02-06T19:04:18Z")
Hi, is there a way to specify a custom GitHub status name/label for a pipeline? We’re reusing a single pipeline for various components in a monorepo that is triggered from a “main” build. Since the pipeline is reused and is for the same commit SHA, it would be nice to customize the status label on the fly through an environment variable or something. We can then declare this in the uploaded pipeline through the `env` key. Or better yet, a root-level `github` key. For example a pipeline YML could be ---
**Author:** ![juanitofatas](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/juanitofatas/32/957_2.png) [@juanitofatas](https://forum.buildkite.community/u/juanitofatas)\ **Post date:** [February 8, 2021, 6:14am UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/2 "2021-02-08T06:14:00Z")
Would be great to see what the example pipeline yaml looks like! ---
**Author:** ![ngan](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ngan/32/662_2.png) [@ngan](https://forum.buildkite.community/u/ngan)\ **Post date:** [February 8, 2021, 8:05am UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/3 "2021-02-08T08:05:26Z")
Doh not sure it got but off… something like: github: status: “buildkite/my-custom-status” steps: … Basically making “github” a top level key. ---
**Author:** ![coderanger](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@coderanger](https://forum.buildkite.community/u/coderanger)\ **Post date:** [February 11, 2021, 10:33am UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/4 "2021-02-11T10:33:30Z")
Shoutout for [Use step key for github status names](https://forum.buildkite.community/t/use-step-key-for-github-status-names/1299) :) It would be nice even for simple usage when using a lot of emoji. ---
**Author:** ![Rose](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/rose/32/834_2.png) [@Rose](https://forum.buildkite.community/u/Rose)\ **Post date:** [February 16, 2021, 4:33am UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/5 "2021-02-16T04:33:02Z")
Hey @ngan! We have a secret (a.k.a. undocumented) alpha feature that might provide what you’re looking for! You can specify a build level notify key like this: ```auto notify: - github_commit_status: context: "whats up!!!" steps: ... ``` And it will alter the github commit status label. Interpolate with env keys as you like! You can also change this at the step like this: ```auto steps: - label: "Example Script" command: "script.sh" artifact_paths: "artifacts/*" agents: queue: "default" notify: - github_commit_status: context: "wow example script!!" ``` But for that to work, you’ll need to uncheck the “Update commit statuses” checkbox on your pipeline’s repository settings page. ![Screen Shot 2021-02-16 at 5.29.20 PM](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/1X/c02992508e943940e8e34292e603b16ae44c9976.png) Hope that solves your issue! I ended up with something like this 😀 ![Screen Shot 2021-02-16 at 5.32.11 PM](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/1X/48bf6c1b7776c24ab2f31156a73c06a4ab00aa6b.png) ---
**Author:** ![ngan](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ngan/32/662_2.png) [@ngan](https://forum.buildkite.community/u/ngan)\ **Post date:** [February 16, 2021, 7:56am UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/6 "2021-02-16T07:56:53Z")
Yes! That’s perfect. One question: when you said you have to uncheck “Update commit statuses,” is that for either usage or just the latter case? ---
**Author:** ![Rose](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/rose/32/834_2.png) [@Rose](https://forum.buildkite.community/u/Rose)\ **Post date:** [February 16, 2021, 8:45pm UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/7 "2021-02-16T20:45:17Z")
Unchecking “Update commit statuses” is just for the latter case! ---
**Author:** ![ngan](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ngan/32/662_2.png) [@ngan](https://forum.buildkite.community/u/ngan)\ **Post date:** [February 27, 2021, 8:04pm UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/8 "2021-02-27T20:04:20Z")
@Rose would it be possible to allow this `notify` for Trigger steps? ---
**Author:** ![sj26](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/sj26/32/17_2.png) [@sj26](https://forum.buildkite.community/u/sj26)\ **Post date:** [February 28, 2021, 11:37pm UTC](https://forum.buildkite.community/t/custom-github-status-name/1447/9 "2021-02-28T23:37:40Z")
Sorry @ngan, notify isn’t supported yet on trigger steps. You can post about it in our feature requests category and we’ll keep track of it and let you know when it works: > **[Features](https://forum.buildkite.community/c/feature-requests/11)** > > Is Buildkite missing something you need? Or maybe you’d like to see us expand on a feature, or have some feedback on an existing feature? We’d love to hear from you!