Benchmark workflow modified to commit results and publish-results workflow added

[deepakdinesh1123]

• publish-results workflow now publishes the benchmarks results to the gh-pages branch
• benchmarks.yml workflow now runs the benchmarks against the last 10 commits and since --skip-existing option is used the exiting benchmarks won't run again

[smithdc1]

The results shared for these systems are all very similar. I'm not sure we need to test on all systems right now. Can we just use Ubuntu for now and can discuss adding the others as a separate PR.

I'm thinking about the environmental impact of running the same thing three times where it is rather unlikely we will see any difference.

I'd be much more interested in seeing results for multiple python versions.

[deepakdinesh1123]

I have added versions 3.10, 3.9, and 3.8. Please let me know which versions I should add

[smithdc1]

OK, looks good to me. Let's merge this, it will be great to start seeing some results. 👀

Suspect I'll need to configure the gh-pages in the settings of this repo. 🤔

[smithdc1]

@deepakdinesh1123 have you seen the action failures with the current version of this PR?

https://github.com/smithdc1/django-asv/actions/runs/2529414916

[deepakdinesh1123]

The benchmark workflow is calling the publish-results workflow which I have added in this PR but it is not in main, I have run this workflow on a PR in my repository here. Once publish-results gets added the workflows can be run

[smithdc1]

The benchmark workflow is calling the publish-results workflow which I have added in this PR but it is not in main, I have run this workflow on a PR in my repository here. Once publish-results gets added the workflows can be run

Thank you for your time to explain this to me.

Let's merge it 👍