Create webpack.yml

[tijuks]

PR Checklist

• Addresses an existing open issue: closes #<the_issue_number_here>.
• You have discussed this issue with the maintainers of the repository, and you are assigned to the issue.
• If it exists, steps in the CONTRIBUTING guide (generally described in the CONTRIBUTING.md file at the root of the repository) were taken.
• The PR title follows the "Conventional Commits" guidelines.

Overview

• Explain the details for making this change: What existing problem does the Pull Request solve? Why is this feature beneficial?
• If your contribution has altered the BPMN rendering or any other visual feature, add screenshots.
• If the Pull Request includes breaking changes, it must explicitly follow the syntax proposed by Conventional Commits (in the PR title and with a quote at this end of this overview).

Notes

N/A

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Pull request title linting 🚨

In order to merge this pull request, the title of the pull request should be prefixed by one of the available types.

Available types:

• build: Changes that affect the build system or external dependencies
• chore: Other changes that don't modify src or test files
• ci: Changes to our CI configuration files and scripts
• docs: Documentation only changes
• feat: A new feature
• fix: A bug fix
• perf: A performance improvement
• refactor: A code change that neither fixes a bug nor adds a feature
• revert: Reverts a previous commit
• style: Changes that do not affect the meaning of the code
• test: Adding missing tests or correcting existing tests

---

Examples

feat(grpc): add new endpoint
refactor: combine class A and class B
ci: update pull request linter
style: change format of strings

💁 For more examples, visit https://www.conventionalcommits.org/en/v1.0.0/#examples.

[tijuks]

Gathering polls seems loñg. Chóre s shoould build now

[tbouffard]

Spammy, I close this PR.

@tijuks please create Pull Requests in your own fork in the future.