Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

improve issue templates#19693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
3ru wants to merge1 commit intowebpack:main
base:main
Choose a base branch
Loading
from3ru:improve-issue-templates-redirect-discussions

Conversation

3ru
Copy link
Contributor

@3ru3ru commentedJul 12, 2025
edited
Loading

Summary

This PR updates webpack to use modern YAML issue templates and attempts to establishes a sustainable ecosystem where Issues are reserved for genuine bugs only. All other inquiries, feature requests, and support questions are directed to GitHub Discussions, creating a community-driven support system where users can help each other find answers and engage in meaningful discussions.

hai-x reacted with thumbs up emoji
@codspeed-hqCodSpeed HQ
Copy link

CodSpeed Performance Report

Merging#19693 willdegrade performances by 95.37%

Comparing3ru:improve-issue-templates-redirect-discussions (8823af1) withmain (ad1e3b4)

Summary

⚡ 3 improvements
❌ 6 regressions
✅ 124 untouched benchmarks

⚠️Please fix the performance issues oracknowledge them on CodSpeed.

Benchmarks breakdown

BenchmarkBASEHEADChange
benchmark "cache-filesystem", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'10.7 ms230.8 ms-95.37%
benchmark "devtool-source-map", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'11.8 ms64.8 ms-81.75%
benchmark "future-defaults", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'11.7 ms46.7 ms-75.05%
benchmark "lodash", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'33.9 ms30.6 ms+10.62%
benchmark "many-chunks-commonjs", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'12 ms62.7 ms-80.87%
benchmark "many-modules-commonjs", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'52.4 ms11.3 ms×4.6
benchmark "many-modules-esm", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'11.2 ms48.5 ms-77%
benchmark "minimal", scenario '{"name":"mode-development","mode":"development"}'24.3 ms30.7 ms-20.63%
benchmark "three-long", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'227 ms13 ms×17

Copy link
Member

@evenstensbergevenstensberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

this looks good, but can you create this in a fork and I'll try the pr manually?

@3ru
Copy link
ContributorAuthor

3ru commentedJul 13, 2025

@evenstensberg
Made it so you can test fromhere!

@alexander-akait
Copy link
Member

@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

3ru reacted with thumbs up emoji

@3ru
Copy link
ContributorAuthor

3ru commentedJul 14, 2025

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?

alexander-akait reacted with thumbs up emoji

@alexander-akait
Copy link
Member

I agree, let's wait@evenstensberg answer

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@evenstensbergevenstensbergevenstensberg left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@3ru@alexander-akait@evenstensberg

[8]ページ先頭

©2009-2025 Movatter.jp