You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a visual indicator to the repositories table to allow users to identify any repositories that are not ready.
Possible Implementation
A possible implementation is to add a new status column as the first column to the repositories table. When the repository is not ready, the PriorityHigh icon shows in the column with the tooltip 'Repository not ready'. Clicking the icon should take you to the repository page, where the user can view why the repository is not ready on the advanced tab (existing functionality).
Context
The user needs to discover if any repositories not ready when looking at the repositories table so the user can take the appropriate actions to make a repository ready. A repository may not be ready for several reasons, including an expired access token, an invalid url, or a private repository registered without an access token.
The text was updated successfully, but these errors were encountered:
Feature Suggestion
Add a visual indicator to the repositories table to allow users to identify any repositories that are not ready.
Possible Implementation
A possible implementation is to add a new status column as the first column to the repositories table. When the repository is not ready, the PriorityHigh icon shows in the column with the tooltip 'Repository not ready'. Clicking the icon should take you to the repository page, where the user can view why the repository is not ready on the advanced tab (existing functionality).
Context
The user needs to discover if any repositories not ready when looking at the repositories table so the user can take the appropriate actions to make a repository ready. A repository may not be ready for several reasons, including an expired access token, an invalid url, or a private repository registered without an access token.
The text was updated successfully, but these errors were encountered: