CodSpeed Performance Report

Merging #19693 will degrade performances by 95.37%

_{Comparing 3ru:improve-issue-templates-redirect-discussions (8823af1) with main (ad1e3b4)}

Summary

⚡ 3 improvements
❌ 6 regressions
✅ 124 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

@evenstensberg
Made it so you can test from here!

@evenstensberg @3ru Good idea to improve such things and I think we need to improve these templates in all our repos, not only in webpack, so some things like version and used webpack packages should be improve too, for webpack org we have - https://github.com/webpack-contrib/css-loader/tree/master/.github/ISSUE_TEMPLATE, so I think we need to look at them too and union with these

for webpack org we have - webpack-contrib/css-loader@master/.github/ISSUE_TEMPLATE, so I think we need to look at them too and union with these

@alexander-akait

Great point about unifying across all webpack repos! Creating a centralized template repository could be a solid approach for overall improvement. We could potentially set up GitHub Actions to automatically generate PRs for updating issue templates across all repositories - that would make maintenance much easier.

I'm happy to take the initiative on this, but given the repository permission requirements, it might make more sense for @evenstensberg to lead this effort. What do you both think?

I agree, let's wait @evenstensberg answer

@3ru sounds good to me, you can even do this manualy but it will take some time

@alexander-akait Let's merge this for now and think separately about overall management of other templates in webpack org. What do you think?