Should we maybe make it required to pass the manda...
# proj-agent
c
Should we maybe make it required to pass the mandatory CI before merging? For example, I don't think this PR ran all CI: https://github.com/OpenHands/software-agent-sdk/pull/2524 A kind of proof: it didn't get to run the creation of agent-server builds: the edit in the PR description with links to builds didn't have time to run. Now I'm not sure how many checks are mandatory, but I do feel that in this case, only very few checks ran... šŸ¤” There's basically no-risk in that PR, but for others it would maybe matter.
That said, there is another detail: • I would slightly still prefer the griffe Python and oasdiff REST APIs checks to not be mandatory, so they don't block PRs as we keep refining them
Same for the unresolved threads workflow, I feel it's best if it annoys agents, but doesn't really block humans
m
A kind of proof: it didn't get to run the creation of agent-server builds: the edit in the PR description with links to builds didn't have time to run.
I believe this is because are not
required
. To merge a PR you have to pass the
required
tests, but these are just sdk-tests , cross-tests, ...
c
I'm trying to say that I suspect things like SDK tests or cross tests are not mandatory for merging
šŸ‘ 1
m
You can check in settings if they are mandatory to merge: https://github.com/OpenHands/software-agent-sdk/settings I cannot check for that as I have just write permissions. But I suspect yes, as you have the label required on these tests.
c
Another example
It looks like they ran, but they ran AFTER the merge
Maybe that's good...
I mean, if in 4 minutes the PR got merged, and this took 7 minutes, it's kinda fun how it compressed time šŸ˜…
I don't have access to CI settings either
m
The test you are speaking about is not required to merge a PR šŸ™‚ So everything was fine
c
OK... Interesting. Maybe we had so many speed improvements that it feels like too fast šŸ˜…
You must be right. I tried to pay attention and not many are required; and those time-consuming are not