Open tvargova opened 3 years ago
The widget takes the most recent run of the build definition, not the repo...and that's an important distinction as it doesn't have any knowledge of the repo or branch you are using. It relies upon the build definition. You could create multiple build definitions pointing at the various branches and use the title to delineate between them using multiple widgets.
The Azure DevOps product team has provided little to no API enhancements over the last 18 months. It's frustrating. I'll look into seeing what it would take to include filtering by branch, but it will boil down to if the API provides me a view into what you're looking for.
This widget is helpful to visualize the code coverage, we appreciate the possibility to display Branch code coverage, but we're running into reporting problems as it's not giving any “filtering mechanism” that could enable us to select only the appropriate release/git branch/tags etc... it just takes the last run of pipelines for the repo. Is there a plan to enhance the widget with a filtering option?
Originally posted by @tvargova in https://github.com/sdavis3/code-coverage-widgets/issues/24#issuecomment-761112515