Publish GIT Revision of running build

[lidel]

Right now we are unable to tell what build is running, which will make bug reporting a real problem.

It would be extremely useful to:

• At least put it in meta header (example)
• Additionally, put a faded-out version somewhere in Settings screen, or near 'See source'/'Report a bug', so it is visible on screenshots and/or non-technical user is able to check it and provide it with a bug report

This needs to happen before we ask general public for feedback.

Eg.

• https://stackoverflow.com/questions/48391897/add-git-information-to-create-react-app
• How to version my app facebook/create-react-app#2486

[fsdiogo]

This is great @lidel 👌

Here's a thought, as we have the running daemon version, why not have the WebUI version there too:

[lidel]

Hm.. I'd rather not put it there: webui version is not really a part of "node info".

What if we add it above links added in #809 (comment) ?
To save space, the git hash (git rev-parse --short HEAD) could double as a link to sources at github eg:
See sources: 1e2c58fe

[fsdiogo]

webui version is not really a part of "node info".

Yeah, you're right.

What if we add it above links added in #809 (comment)?

That could work, although personally I wouldn't want that info showing all the time. I'd prefer as you said somewhere in Settings. Or in the status page maybe?

[fsdiogo]

Well, something along these lines doesn't shock me!

[olizilla]

Very cool! What if we go more subtle and replace "see the code" with the revision number?

[fsdiogo]

I have mixed feelings about that 🤔

For one I like it because it would have -1 link. On the other hand, it's not very clear for the average user that the revision number will link to the code, and I think we should always have a direct link to the latest code.

Do you agree?

[olizilla]

that's reasonable. I can get behind being extra explicit here.

[fsdiogo]

Cool, I'll open a PR.

What will be the plan to update the git revision?

Here it is: #844