Feature Request: Add support for analysing all non-main branches

[Ezard]

It would be awesome if we could analyse tasks that are run in pull request pipelines, i.e. any task that is run in CI but isn't run on the main branch

This would allow us to track performance that relates to the speed at which PRs can be merged

Perhaps this could be supported by adding a negation modifier to the --branch flag when generating a report, e.g. !main

./gradlew reportAnalytics --branch="!main" --task="test" --period="1y"

This would match every branch that is not named main

[janbarari]

It would be awesome if we could analyse tasks that are run in pull request pipelines, i.e. any task that is run in CI but isn't run on the main branch

This would allow us to track performance that relates to the speed at which PRs can be merged

Perhaps this could be supported by adding a negation modifier to the --branch flag when generating a report, e.g. !main

./gradlew reportAnalytics --branch="!main" --task="test" --period="1y"

This would match every branch that is not named main

Hi @Ezard
Thank you for sending your feedback
I put this ticket to investigation process

Best
Mehdi

[Ezard]

@janbarari I've had a look into how the plugin works, and I believe that I could add this functionality myself if you're open to me submitting a PR 🙂

If you are, then do you agree with my above suggestion for how it could be implemented, or would you rather that a different route was taken?