Ingo Mohr

> @ingomohr I'm not sure why I'm currently unable to assign you to this issue. [Maybe try commenting on it?](https://github.blog/2019-06-25-assign-issues-to-issue-commenters/) I've read that you can assign to non-collaborators once they've...

> @ingomohr there we go ;) Nice. Didn't know that restriction, either. I thought (at first) you could only assign to collaborators - but this is nice. :)

> @ingomohr now that #90 is merged, do you think I can close this? Or do you want me to leave it open in the event you come up with...

But I'd be fine w/ closing, as well.

> @ingomohr I just created a new branch and unfortunately no new update site branch was created. Maybe it has to due with the way I named the branch? https://github.com/AObuchow/Eclipse-Spectrum-Theme/blob/master/.github/workflows/build-updatesite-branches.yml#L9...

@AObuchow The „experimental“ branch has the same HEAD commit as the „master“ has. So, I think we could fix this by adding a new trigger for the workflow. There should...

Ok, here's a small update. It's possible to run the workflow when a branch has been created. - And it should be possible to add that trigger to the workflow....

Some info seems to be missing. @AObuchow discussed some things via DM on Twitter. Here's the update: * Updatesites are built automatically for every branch including master, now. * PR-updatesites...

The PR build workflow should also merge the dev branch into the target branch (locally repo on the build machine, of course :) ) to check that... * a) ......