Skip to content

Issues: Automattic/woocommerce-payments

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
7 Open 4 Closed
7 Open 4 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Plugin: Fix unused parameter phpcs sniffs focus: architecture Product architecture and engineering best practices priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: technical debt This issue/PR represents/solves the technical debt of the project.
#8654 opened Apr 17, 2024 by reykjalin
Plugin: Fix unused parameter phpcs sniffs in tests focus: architecture Product architecture and engineering best practices priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: technical debt This issue/PR represents/solves the technical debt of the project.
#8653 opened Apr 17, 2024 by reykjalin
Plugin: Fix WooCommerce hook comment phpcs reports focus: architecture Product architecture and engineering best practices priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: documentation This issue is a request for better documentation. type: technical debt This issue/PR represents/solves the technical debt of the project.
#8554 opened Apr 1, 2024 by reykjalin
2
Plugin: Fix reserved keyword variable names phpcs reports focus: architecture Product architecture and engineering best practices good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: technical debt This issue/PR represents/solves the technical debt of the project.
#8543 opened Apr 1, 2024 by reykjalin
Subscriptions: Fix reserved keyword variable names phpcs reports focus: architecture Product architecture and engineering best practices good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: technical debt This issue/PR represents/solves the technical debt of the project.
#8540 opened Apr 1, 2024 by reykjalin
1
Change storage for webhook events component: webhooks focus: architecture Product architecture and engineering best practices type: good for architectural review This issue/PR is related to / good for architectural review. type: technical debt This issue/PR represents/solves the technical debt of the project.
#5374 opened Jan 6, 2023 by htdat
2
Smarter error messages for faster troubleshooting category: ops Features for product operations without touching code. focus: architecture Product architecture and engineering best practices needs feedback The issue/PR needs a response from any of the parties involved in the issue. type: enhancement The issue is a request for an enhancement. type: good for architectural review This issue/PR is related to / good for architectural review.
#1346 opened Feb 18, 2021 by jessepearson
3
ProTip! Add no:assignee to see everything that’s not assigned.