# Docker Manager - remote commit hash should diff vs the installed version

**URL:** https://meta.discourse.org/t/docker-manager-remote-commit-hash-should-diff-vs-the-installed-version/87832
**Category:** Feature
**Created:** [May 18, 2018, 1:56pm UTC](https://meta.discourse.org/t/docker-manager-remote-commit-hash-should-diff-vs-the-installed-version/87832 "2018-05-18T13:56:09Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Maisy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/maisy/32/119902_2.png) [@Maisy](https://meta.discourse.org/u/Maisy)
#### Post date: [May 18, 2018, 1:56pm UTC](https://meta.discourse.org/t/docker-manager-remote-commit-hash-should-diff-vs-the-installed-version/87832/1 "2018-05-18T13:56:09Z")

</div>

Just had a bit of a brainwave regarding the Docker Manager.

At present, when you see an update in the Docker Manager, you have the option of clicking on the commit hash of the new version:

 ![05](https://global.discourse-cdn.com/meta/original/3X/0/a/0a25cac890acbda9a2c0e1c07a88fbab0e644f53.png)

I would expect this to compare against the version currently installed, however, it seems to compare against **tests-passed**. What this means is that when you click on it, you see this:

 ![42](https://global.discourse-cdn.com/meta/original/3X/e/3/e363a158a7830dcb5fab0c802ac9b187817075a8.png)

I’m sure you can agree that this isn’t particularly helpful. What I would propose instead is that clicking on the new commit hash should compare vs the installed version.

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [May 18, 2018, 2:27pm UTC](https://meta.discourse.org/t/docker-manager-remote-commit-hash-should-diff-vs-the-installed-version/87832/2 "2018-05-18T14:27:16Z")

</div>

Click the one under the repo name, that does exactly what you are seeking.

---

<div class="post-metadata">

### Author: ![Maisy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/maisy/32/119902_2.png) [@Maisy](https://meta.discourse.org/u/Maisy)
#### Post date: [May 18, 2018, 3:08pm UTC](https://meta.discourse.org/t/docker-manager-remote-commit-hash-should-diff-vs-the-installed-version/87832/3 "2018-05-18T15:08:14Z")

</div>

I am aware of this, but why have a hyperlink on the remote version that always goes to a dud compare page? I realise it is trying to be helpful and does so when you click on the installed commit, but this helpfulness doesn’t carry over to the latest commit.

It should either go to the commit summary, or it should diff vs the installed version. Otherwise it just shouldn’t be a link.

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [May 18, 2018, 6:46pm UTC](https://meta.discourse.org/t/docker-manager-remote-commit-hash-should-diff-vs-the-installed-version/87832/4 "2018-05-18T18:46:05Z")

</div>

> [@Maisy](#):
>
> It should either go to the commit summary

This, this is where I would think it should go. It should summarize the commit the remote version is on. Primarily because it is a descriptor of the remote server, not the local version, but that is just my opinion.