Tobias Roeser

So, this change is all about _not_ running draft PR events but run all push events in any branch instead. It looks to me, that we now run all commits...

I started to open PRs from the main repository, since this allows scenarios like opening PRs against another PR branch, which gets autoamtically rebased to `main`, once the dependency got...

We already have a dependency on `jarajar-abrams` to provide the `Relocate` assembly rule. https://github.com/com-lihaoyi/mill/blob/b66ef93e3ca926f480555040c9726814662cc97e/scalalib/src/mill/scalalib/Assembly.scala#L81

The dependency going to be shaded should be declared as `compileIvyDeps` or `compileModuleDeps`.

Marking this ready for review, to see CI results.

Easiest reproducer of the classlaoding issue: ```console > mill example.scalalib.basic[3-simple] ... 8716] example.scalalib.basic.3-simple.packaged.daemon.testForked Running Test Class mill.testkit.UtestExampleTestSuite 8716] -------------------------------- Running Tests -------------------------------- 8716] Preparing integration test in /home/lefou/work/opensource/mill/out/example/scalalib/basic/3-simple/packaged/daemon/testForked.dest/sandbox/run-1 8716] 8716]...

Reported upstream: * https://github.com/sbt/zinc/issues/1623

See also * https://github.com/com-lihaoyi/mill/issues/6039

This issue isn't solved. > The help message displayed is the default one logged by `mainargs.Parser(this).runOrExit`. I am not sure what needs to change here. Could you elaborate? What looks...

So, the output probably depends on the contents of the workding dir, since I see this in an empty directory. ```console > mill init --help Using mill version 1.1.0-RC1 [build.mill-59/64]...