Clearly display last sync time on repository and file views

[rrhyne]

Details

Several users have reported questions about the last update time of the repositories and files in their search results. See this Slack thread for a collection of issues:

https://sourcegraph.slack.com/archives/C0HMGV90V/p1609797067109900

Users generally:

• want to know if the file they are looking at in Sourcegraph is current with its status in their code host
• want to know if the repository they are viewing was cloned or synced after their last commit

In the case of the repository or file being out of sync, the user:

• would like to know when the repository will next be synced or alternatively be able to trigger a sync

Proposed solution

This information currently exists on the repository/settings/mirroring and cloning page, but it is only viewable by site admins.

Adding the value from the Last refreshed: time on the file view and on the repository home page will give users more confidence in their search results or the ability to spot an issue with their results.

Consider renaming Last refreshed: to 'Last synced' to be consistent with how this functionality is discussed in the system status notifications.

Additionally, we should consider providing the user with a way to manually trigger a sync. This would reduce friction around our inability to state when the next sync time will occur and facilitate the resolution of their current search requirements.

Type of debt

• UX - inconsistent experiences throughout the product that negatively impacts the learnability and integrity of the flow

Estimated amount of work

1 day design?
1 day development?

Areas affected

• Repository pages
• File view pages

Impact

Affects the user's trust in the accuracy of the data they are viewing

Urgency

If the resolution is to display the sync time only, this could be addressed in 1 to 2 releases.

[github-actions]

Heads up @Joelkw @felixfbecker @jeanduplessis - the "team/web" label was applied to this issue.

[github-actions]

Heads up @AlicjaSuska @felixfbecker @umpox @valerybugakov @5h1rU @pdubroy - the "team/frontend-platform" label was applied to this issue.

[taylorsperry]

Hey, @rrhyne, FPT is going through backlog UI issues to see what might be worth picking up for core workflow improvements. Sanity check on this, since I know it's pretty old:

1. We currently display the time of last sync in search results (on hover):

2. We do not show the time of last sync on the repo home page (I don't see it here)

3. And we do not show the time of last sync on a file page (I don't see it here)

4. We do not have a way to trigger a sync or see when the next sync will happen.

If (if!) this is something that we were to pick up (we're working with @benvenker to prioritize), we would need design input to take on 2, 3, and 4. What would be the level of effort for your group?

[rrhyne]

Small level of effort. Return is trust. It isn't the information that is used often, but when it counts, it's unavailable in the product.