# DRONE\_COMMIT\_MESSAGE is not updated in PR events

**URL:** <https://drone.discourse.group/t/drone-commit-message-is-not-updated-in-pr-events/11034>\
**Category:** Drone Support\
**Created:** [March 8, 2018, 12:36pm UTC](https://drone.discourse.group/t/drone-commit-message-is-not-updated-in-pr-events/11034 "2018-03-08T12:36:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jvican](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jvican/32/3733_2.png) [@jvican](https://drone.discourse.group/u/jvican)\
**Post date:** [March 8, 2018, 12:36pm UTC](https://drone.discourse.group/t/drone-commit-message-is-not-updated-in-pr-events/11034/1 "2018-03-08T12:36:13Z")

</div>

Hello,

I’m using some keywords in my commit message to modify the CI logic. The CI logic runs in the PR events.

I’ve just realised that Drone does not update the `DRONE_COMMIT_MESSAGE` environment variable when there are subsequent commits added to a PR, and therefore the logic of my CI is always decided upon the commit message of the first commit, not the subsequent one.

Cheers,

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [March 8, 2018, 3:29pm UTC](https://drone.discourse.group/t/drone-commit-message-is-not-updated-in-pr-events/11034/2 "2018-03-08T15:29:53Z")

</div>

the `DRONE_COMMIT_MESSAGE` is populated from the `pull_request.title` field in the pull request webhook. We do not capture the individual git commit message for pull requests.

---

<div class="post-metadata">

**Author:** ![jvican](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jvican/32/3733_2.png) [@jvican](https://drone.discourse.group/u/jvican)\
**Post date:** [March 8, 2018, 3:41pm UTC](https://drone.discourse.group/t/drone-commit-message-is-not-updated-in-pr-events/11034/3 "2018-03-08T15:41:42Z")

</div>

Could that use case be accommodated? It seems really weird that `DRONE_COMMIT_MESSAGE` takes the drone PR title. In that case, I would expect the commit message to be empty and the current value to be bound to `DRONE_PR_TITLE`.

However, I see no reason why `DRONE_COMMIT_MESSAGE` is not correctly populated.

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [March 8, 2018, 3:43pm UTC](https://drone.discourse.group/t/drone-commit-message-is-not-updated-in-pr-events/11034/4 "2018-03-08T15:43:10Z")

</div>

yes, we can consider capturing the git commit message field in a future release.

---

<div class="post-metadata">

**Author:** ![kondei](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/kondei/32/4839_2.png) [@kondei](https://drone.discourse.group/u/kondei)\
**Post date:** [October 31, 2018, 3:23am UTC](https://drone.discourse.group/t/drone-commit-message-is-not-updated-in-pr-events/11034/5 "2018-10-31T03:23:20Z")

</div>

I was confused about this behavior.  
I tryed to use “[CI SKIP]” commit message explained in “Skip Commits” in [http://docs.drone.io/hooks/#skip-commits](http://docs.drone.io/hooks/#skip-commits), but it does not work.  
I think this is because DRONE\_COMMIT\_MESSAGE is pull\_request.title when the hook event is pull\_request.