# Feature Request Auto-Commit

**URL:** <https://discourse.nodered.org/t/feature-request-auto-commit/36411>\
**Category:** General\
**Created:** [23 November 2020 17:08 UTC](https://discourse.nodered.org/t/feature-request-auto-commit/36411 "2020-11-23T17:08:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![crackytsi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/crackytsi/32/28369_2.png) [@crackytsi](https://discourse.nodered.org/u/crackytsi)\
**Post date:** [23 November 2020 17:08 UTC](https://discourse.nodered.org/t/feature-request-auto-commit/36411/1 "2020-11-23T17:08:23Z")

</div>

I like the newly introduced auto-commit feature since version 1.2. Really cool! Thank you very much.

It would be even more nice, if I there would be an option, that asks me on every deploy what I have changed and use that input for the commit change log.  
Is this something that makes sense or is planned?

best regards

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [23 November 2020 17:34 UTC](https://discourse.nodered.org/t/feature-request-auto-commit/36411/2 "2020-11-23T17:34:35Z")

</div>

I decided against doing that for the simple workflow as being prompted every time you hit the deploy button would soon get annoying whilst you've actively developing/testing a flow. That was the overwhelming feedback we got when I originally floated the idea of the simple workflow.

I've no doubt there will be a way to balance the two - but as yet, it hasn't presented itself.

One option, that git allows, is to amend the last commit's message. As long as you haven't pushed the commit to a remote yet, then we could build in something to support that; so you can continue clicking Deploy as much as you want, with a new commit being created each time, but when you do something note-worthy, you can amend its commit after clicking deploy.

---

<div class="post-metadata">

**Author:** ![crackytsi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/crackytsi/32/28369_2.png) [@crackytsi](https://discourse.nodered.org/u/crackytsi)\
**Post date:** [24 November 2020 10:17 UTC](https://discourse.nodered.org/t/feature-request-auto-commit/36411/3 "2020-11-24T10:17:33Z")

</div>

Thanks @knolleary I fully understand that. Thanks for sharing your thoughts 🙂

Of course an alternative option could be to have two buttons:  
Deploy and Deploy&CheckIn

Your idear of changing the the last commit message later (before remote push) also sounds nice. I just have to add that I guess from operation perspective this makes it easier to loose overview and find a specific commit, as you have several "Standard-Commit-Log" commits in between your "relevant" commits 😉

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [23 January 2021 10:17 UTC](https://discourse.nodered.org/t/feature-request-auto-commit/36411/4 "2021-01-23T10:17:35Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.