add LLVM 18.x as a git submodule

[kvpanch]

This changeset is based on #346

[kvpanch]

@xermicus now it's good to go

[xermicus]

Thanks, very nice! Two things stick out:

• The submodule should only be required in LLVM test and release workflows?
• The Test LLVM Builder action doesn't seem being run in this PR. But it should surely have been triggered based on this change set?

[xermicus]

Maybe this should run when the .gitmodules has changed?

[kvpanch]

The file no longer exists. The way it suppose to work in future is we update new llvm file with new commit to pull from LLVM

[xermicus]

Same here, shouldn't be needed?

[kvpanch]

let me try to remove it

[xermicus]

Oh no - the LLVM builder workflow not showing up is due to an invalid spec: https://github.com/paritytech/revive/actions/runs/19039292406

This isn't this PR's fault but would you mind fixing it here at the same time as drive-by?

[kvpanch]

Oh no - the LLVM builder workflow not showing up is due to an invalid spec: https://github.com/paritytech/revive/actions/runs/19039292406

This isn't this PR's fault but would you mind fixing it here at the same time as drive-by?

interesting. The error complain about path and path-ignore, but the structure there didn't change, not sure what happens

[xermicus]

The problem is that we can only have either paths or paths-ignore defined.

From my side there is no need to bikeshed this. Just remove paths-ignore to fix it. It was intended as a minor convenience tweak but it's not the end of the world if we run the workflow for markdown changes.

I didn't catch this during reviewing the PR introducing the regression. The docs would have explained that but of course I didn't read them careful enough. It's really unfortunate (and also very surprising to me) that in the PR itself there seems to be no indicator whatsoever if there are invalid workflow yml files found 😒