Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'x' days ago is not a useful information in commit list. #816

Open
hansgru opened this issue Jul 6, 2015 · 2 comments · May be fixed by #1990
Open

'x' days ago is not a useful information in commit list. #816

hansgru opened this issue Jul 6, 2015 · 2 comments · May be fixed by #1990

Comments

@hansgru
Copy link

hansgru commented Jul 6, 2015

Maybe it looks nice in "recent activity" but in the commit history, the "'x' days ago" information is not useful at all. Please put the timestamp there.

See in the screenshot below:
gitbucket_commit_time

how not helpful at all is the information "2 days ago" and "3 days ago". More practical would have been to have the time, since the commits are grouped by date. Of course, after the date, one could extend with the text of how much time is that date in the past, but for single commits the timestamp is more helpful.

This is of course how GitHub works, but IMHO GitBucket should not "clone" the bugs too :).

Thank you.

@takezoe
Copy link
Member

takezoe commented Jul 13, 2015

Elapsed time notation such as "2 days ago" is application internationalization technic. It's useful for global teams which have developers in different timezone. And you can confirm timestamp at tooltip as same as GitHub.

@eprozium
Copy link

eprozium commented Sep 2, 2016

Make the other way round: put the timestamp in the list and the X days in the tooltip, since as the author mentions, the commits are already grouped by days, so that information is superfluous.

@kounoike kounoike linked a pull request Apr 29, 2018 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants