Running tests without a PR?

Thomas Stüfe thomas.stuefe at
Tue Sep 22 12:33:44 UTC 2020

Hi Robin,

On Tue, Sep 22, 2020 at 2:14 PM Robin Westberg <robin.westberg at>

> Hi Thomas,
> We’re hoping that most of what the submit-repo provided can instead be
> serviced by GitHub Actions in the near future (see
> - these tests can run directly
> on a branch before creating a PR.
This seems like a very useful feature. Especially if you manage to be less
opaque about build/test errors than jdk-submit had been :)

> Otherwise, as you have seen, any commands such as /test do indeed require
> a PR. In these cases you can usually use a “draft” PR though, which won’t
> cause any RFR emails to be sent until it leaves the draft state. So in such
> a PR it doesn’t really matter if you make multiple commits, you can just
> squash them together before making the PR non-draft.

So, in a PR in draft state I still can change history (Rebase, squash,
whatnot)? Just asking since AFAIK a PR in review should not be rebased

Thanks, Thomas

> Best regards,
> Robin
> On 22 Sep 2020, at 13:27, Thomas Stüfe <thomas.stuefe at> wrote:
> Hi,
> Sorry if that question has been answered already, but I cannot find
> anything about it on the wiki.
> If I understand correctly, the old functionality of jdk-submit is now
> covered by the PR command /test? But to run that I need to have an actual
> PR?
> Is there a way to run the tests without opening a PR?
> There are several scenarios where this may be useful. For instance, running
> the tests before creating a PR prevents polluting the PR with follow up
> fixes.
> Thanks, Thomas

More information about the skara-dev mailing list