Developers using Harness Code may not have a need to navigate outside of the Code Repo context in the Harness UI. Today, they have to navigate to the Pipelines context to see the execution history and filter for their code repo. Harness has the trigger activity history for a pipeline. In that data is the code repository that caused the trigger to fire. There would be a better and more intuitive user experience for developers if the pipeline execution history related to a code repo was shown in the code repo context.