| name | wdio-contribution-invite |
| description | Invite issue authors or the community to fix easy webdriverio/webdriverio bugs or docs, including Open Collective / expensable contribution language. Use when investigation shows a localized, confirmed issue.
|
WDIO contribution invite
Load after a time-boxed investigation confirms an easy, real WDIO bug or a
tiny docs fix. See also
triage-playbook.md.
When to invite
- Localized fix (one package / clear function / obvious incorrect behavior)
- Clear reproduction
- Not upstream-only Chrome/Appium/Node
- Docs typo or broken link (invite immediately; little/no code dig)
Labels
- Add
help wanted and/or good first pick when appropriate
- Do not apply
Expensable $… in v1 — maintainers set amounts
Language (from real threads)
Docs/chore:
Thanks for flagging, want to raise a PR for this?
Easy bug:
Any contributions that resolve this bug are appreciated.
Capacity / no timeline:
Any contributions are welcome!
Expense-aware (when encouraging community work on a scoped bug):
This looks like a good candidate for an expensed contribution. WebdriverIO
expenses accepted PRs via Open Collective — a maintainer can apply an
Expensable $… label and run the expense workflow after merge. Please follow
CONTRIBUTING.md
(pnpm install, pnpm run setup, focused tests).
Include short findings (files/symbols) so the author knows where to start.
Ping @author.