Benjamin Bossan

> I tried in a new repo, and things seem to work as expected I invited you to my repo. It still doesn't work there, even though I copy-pasted your...

> Maybe merge the two workflows under the same one, just two different jobs? I copied your exact workflow (only changed repo name) and still the exact same issue: https://github.com/BenjaminBossan/mops/pull/2...

Okay, so where do we go from here? To recap, none of the suggested methods seem to work for getting the commit message for "pull_request" triggers.

+1 on being more explicit about black. It seems, however, that people are not really following the CONTRIBUTING.rst :( We even have a link to it in the README.rst and...

No, we should add something to https://github.com/skops-dev/skops/tree/main/examples and possibly also upload skops models to the Hub.

I believe the simplest implementation would be to have `transform` do what `predict_proba` currently does. The problem that we may want to return an intermediate result and avoid having to...

> Not sure what you mean with "internal validation" ? I meant exactly the thing that skorch does where it splits off some data as a validation set for early...

Another solution that I could think of is something along this line: Suppose we had a context manager that allows to temporarily switch out the `module_` attribute of `NeuralNet` et...

I'm a bit rusty on this issue, so let me try to summarize the constraints we should consider: 1. AFAICT, sklearn will check whether the estimator has a `transform` attribute...

@guybuk I understand your general idea but not all the details. What function are you talking about when you mention `load_params(strict=...)`? I don't see any function with that name and...