Michael Bien

> > if a workflow is manually triggered via workflow_dispatch it can't access the pr-context since there is none, > > Does re-run all jobs not work after relabelling then?...

update: workflow_dispatch can only run on regular branches (e.g master). You can't select PR branches in the UI. So i can skip testing the rest.

> OK, second thought. Does changing the pull request event types to include `labeled` work? https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request this would trigger a new run every time a label is added which is...

but what if we abuse `reopened` for this? there is also "unlocked" which we will probably also rarely use

> > this would trigger a new run every time a label is added which is probably too much since we have also the do-not-merge label etc > > Given...

ready to integrate from my side. Added the "unlocked" trigger and put a info line into the PR template. I think its better to integrate it as is without squashing...

- updated the label descriptions for labels which influence CI. Description text has been prefixed with [ci] which allows filtering. - Added a screenshot with an example to the PR....

merging. Going to send the [NOTICE] mail to the dev list too as @neilcsmith-net advised.

Hi @brutzman, the tutorial page is already marked with "needs review" (although the link to jira is a bit outdated). Filing another issue is redundant. You can simply click "edit...

> @mbien just realised that one of the JARs listed above that has a lot of MRJ affected classes is lucene. Anything of concern? Possible source of any current issues?...