Problem:

Navigation to PipelineRuns require extra clicks that lead to tedious back and forth between views since they happen frequently when a developer pushes code to a repository.

Examples of the navigation UX issues:

• For Git repositories, in majority of cases user wants to get to the list of latest pipelineruns for the repository. She though has to always land on the repository details page, and then click on pipelineruns tab to get to that view. 
• Once user finds the pipelinerun she is looking for, in many cases she would check logs. The logs view is a deadend from the navigation perspective as there is no intuitive path for getting back to the repository view, or the list of pipelineruns for the repository, or the pipeline view, or the list of pipelineruns of a pipeline. The intuitive view to go to is the list of "all" pipelineruns in the namespace. 
• If user is using pipelines as code, there is no way to get to the repositories with a single click, like it is for the pipelines. Every single time she has to first click on "Pipelines" on the left navigation side-bar and then again on the "Repositories" tab

Acceptance criteria:

1. In the Dev perspective, remember the selected tab (per user) on the Pipelines page. When returning to the Pipelines page, set the selected tab appropriately
2. PipelineRuns should be the default tab of the Repository details page, unless they are coming from the Create Git Repository flow.
3. When coming from the Create Git Repository flow (from any perspective), bring the user to the Details tab of the Repository details page.

Dependencies (External/Internal):

Epic Exploration

Held November 15th: Miro

Notes

1. In the Admin perspective, we will not be saving the selected tab on the Pipelines page. There are many tabbed pages in the Admin perspective. From a consistency perspective, there should be an epic to address all of these pages in bulk.