`Development`: Add git commit to navbar version in dev mode

[TheZoker]

Checklist

General

• [ ] I tested all changes and their related features with all corresponding user types on a test server.
• [x] This is a small issue that I tested locally
• [x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• [x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

Description

This adds a git commit id into the header, when Artemis is run in development mode.

Not displayed in the prod mode:

Steps for Testing

1. Start Artemis in dev mode
2. Have a look at the version in the header

Review Progress

Code Review

• [ ] Review 1
• [ ] Review 2

Manual Tests

• [ ] Test 1
• [ ] Test 2

Test Coverage

Class/File	Branch	Line

Screenshots

[TheZoker]

I removed the additional service and moved to the already existing profile service. Thanks for the hints!

Since this PR, you can see which branch was used by just visiting the /managment/info page and it will tell you a lot of information. I think having the git commit in the header when in dev (as suggested by Stefan) is a good idea and if you want to have more information about git, you can look it up in the mentioned endpoint. And this PR also added the branch name to the startup log.

[TheZoker]

Thanks for the suggestion. I moved the git commit id into a tooltip:

It is now displayed for both dev and prod systems

[krusche]

I would display the branch name immediately on dev and test systems. The commit id should be shown in a tooltip on such systems.

On production systems, we should not show the commit as tooltip!

Instead, I suggest to show the branch and commit id in the bottom of the about page.

[TheZoker]

@krusche Where should be branch name be displayed for the dev and test system?

[krusche]

I would display it directly right to the version number

[TheZoker]

The branch name in the navbar (I moved it below the version number, since the branch name could be longer and then clashes with the right menu):

On mobile devices and on production system, the branch name will be hidden.

And the about page:

[github-actions[bot]]

There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions.

[bassner]

Well, yes, this is messing up the breakpoints; if you're adding stuff to the navbar that consumes width, the calculation for the breakpoints needs to be adjusted here.

At best, I could hover over the version and a tooltip would show me commit id and branch name.

This would probably be the simplest solution for that problem

https://user-images.githubusercontent.com/23171488/192281821-38cf5bfd-f56d-494f-a0bc-e239492dd69d.mov

[TheZoker]

Thanks for the hint! The hover style was actually the first approach.

@krusche Should I revert it back to hover or do you want to display the information right away?

[krusche]

Thanks for the hint! The hover style was actually the first approach.

@krusche Should I revert it back to hover or do you want to display the information right away?

If it is too complicated to show it in the navbar directly, then I suggest to add it to the bottom of the page (branch + git commit) above or below the following footer

Of course, this should only be shown for dev and test environments

If you want to show it additionally when hovering over the version, this would be fine for me, but I'd like to see it quickly on dev and test environments without the need to move the mouse ;-)

[krusche]

I would change Git Commit ID: a8482b6 to simply Git commit: a8482b6

[github-actions[bot]]

There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions.