# Revert feature in Docker manager?

**URL:** https://meta.discourse.org/t/revert-feature-in-docker-manager/16363
**Category:** Feature
**Created:** [June 9, 2014, 4:39pm UTC](https://meta.discourse.org/t/revert-feature-in-docker-manager/16363 "2014-06-09T16:39:40Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![stealthii](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stealthii/32/122550_2.png) [@stealthii](https://meta.discourse.org/u/stealthii)
#### Post date: [June 9, 2014, 4:39pm UTC](https://meta.discourse.org/t/revert-feature-in-docker-manager/16363/1 "2014-06-09T16:39:40Z")

</div>

Sometimes the latest commit will leave a broken discourse setup (like right now), but will apply fine, as the rake tasks will complete successfully. It would be nice to have a ‘revert to previous used commit’, until Discourse has a fully comprehensive way of testing an upgrade.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 9, 2014, 11:46pm UTC](https://meta.discourse.org/t/revert-feature-in-docker-manager/16363/2 "2014-06-09T23:46:02Z")

</div>

@eviltrout is going to change it so the Docker update only pulls from the branch of code that passes the smoke tests, which is the way it should have been anyway..

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [December 4, 2025, 11:14am UTC](https://meta.discourse.org/t/revert-feature-in-docker-manager/16363/3 "2025-12-04T11:14:26Z")

</div>