add a workflow check for duplicate mpackage filenames

[ZookaOnGit]

to prevent overwrites of packages accidently named the same, add a check to the validation workflow to see whether the previous author is the same as the current author, and issue a warning if not

[SlySven]

What counts as "accidentally named the same" - what happens if a module in one profile is loaded from a file in a different location in the file system(s) has the same name as a copy which is loaded from a different place?

:worried:

[ZookaOnGit]

just checking package names, ie. cannot have two entirely different implementations of a package called my-gui.mpackage

what happens if a module in one profile is loaded from a file in a different location in the file system(s) has the same name as a copy which is loaded from a different place?

We cannot prevent this unfortunately. It is the same that would happen by the user importing a package manually themselves.