You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While GitHub Checks are always against a commit SHA, there are two different kinds of checks we could do, PR checks and commit checks. Should both of those be considered v1? It sort of depends on where we think this will be tried out first.
Yeah, if I'm going to try and connect it to CSSWG, we do most of our work outside of PRs, so the commit check is more useful. We def want to do PRs as well, but we want to then automatically pass the commit checks when the PR is merged, if the PR checks passed. That'll need the db backing.
So if v1 doesn't include the db, then I think we need to decide between commit and PR checks for now, and not do both.
So I'm thinking let's do only commit checks as a starting point then, that's more low-level than PRs and likely will result in reusable building blocks for PRs later.
The text was updated successfully, but these errors were encountered: