Create website schema validation workflow

[SenseException]

No description provided.

[SenseException]

Next to some failing static analysis workflows, the newly added website-config vlidation fails because 2.x isn't a coherent branch format compared to the other repositories. Should the branch name be changed or should the validation itself allow formats like 2.x?

[dbu]

what branch naming do the other repositories do, is there a branch naming policy documented somewhere? we can change to that, i don't mind.

[SenseException]

I don't think we have a fix branch naming policy. Other repositories have branch names like 2.0.x, 2.1.x, and so on. At least the ones that have a documentation. If we can agree on this format, I can provide a documentation about the branch names.

[dbu]

i renamed 2.x to 2.0.x and 1.x to 1.5.x

i hope i won't forget to create 2.1.x before merging new features 😅

[dbu]

and fixing the CS issues in #874

[dbu]

can you pleaes rebase this branch? i expect it to become all green :-D

[greg0ire]

@dbu rebasing is not necessary, closing and reopening is enough. The build failure shows that we should update .doctrine-project.json with the new names.

[dbu]

cool, thanks for the cleaning up