Open brucealdridge opened 2 years ago
@mattallan Interested in your thoughts on what checks are most useful/essential for subs-core. Also the relationship to other repos: what checks do we get for free from WCPay or subs pro repo.
Pinging in @aprea since you're our DRI for patch release follow up. This issue could address one of the patch follow up items - can you confirm what's most urgent here with @mattallan. We can iterate and add more checks in future, for now the most important thing is to get something in place to cover gaps identified in 3.2.x. cc @brucealdridge
Interested in your thoughts on what checks are most useful/essential for subs-core.
I think the most important thing is to get some PHP linting checks for the various PHP version. This was the major breaking point we saw when releasing 3.2 and is probably one of the easier things to check so I would say having that is a good starting point!
I'm not too fussed on other easy things to add like psalm at this point.
Also the relationship to other repos: what checks do we get for free from WCPay or subs pro repo.
In WC Payments most of their checks ignore the subscriptions-core files so we don't get anything for free there. Maybe the E2E tests in wcpay will technically have WCS Core enabled 🤔
We can iterate and add more checks in future, for now the most important thing is to get something in place to cover gaps
Yeah, I definitely agree with this!
Here's my 2c on how I would order/prioritize these:
I'm probably missing something obvious in that list, but what's everyone's thoughts on that or?
That looks like a solid list @mattallan, I'm happy with that as a starting point 👍
This is great, @brucealdridge! I just added to the bottom of the list to enforce code coverage, something similar to https://github.com/Automattic/woocommerce-payments/pull/2342.
Just noting that I've moved this back to the in-progress pipeline now that the first PR was merged. But feel free to push it back if this isn't something you're looking into.
Just noting that I've moved this back to the in-progress pipeline now that the first PR was merged. But feel free to push it back if this isn't something you're looking into.
+1, happy for this to go to Icebox
or New issues
while we're focused on sprint & projects. We can iterate on this over time.
Shifting this to Icebox now we're out of cooldown - though we've made some great progress here!
Hey @brucealdridge, FYI, I have checked the JS linting
and Have some of these checks run on pre-commit (similar to WC Payments)
checkboxes in the PR description.
I believe these were completed in #57?
Apologies if that's not the case and feel free to uncheck them if there's something pending.
Marking as low – definitely keen for improvements here but this is an internal task (not impacting merchants).
Description
Add automated checks to pull requests to make submissions and reviewing easier.
Checks to add