@miqui I don't have merge permissions, so you'll need to perform the merge. Thanks.

I am hesitant to merge this as umbrelladocs/action-linkspector@v1 uses Linkspector v0.5.3 which randomly flags correct links as broken in src/oas.md in the development branches.

@ralfhandl I think among all of us, you have the most experience with that tooling. I was just trying to unblock work on both this repository and the Overlays one. If you're satisfied with the current approach (pinning the version, using an npm script), I'll replicate that to overlays. Just let me know.

The target is using the action and the latest Linkspector version. If that works for Overlays, just keep it.

I don't know why Linkspector 0.5.3 behaves so erratic for the OAS markdown source file - maybe it is "too large"?

This needs some experimenting, but "unfortunately" I can easily find more interesting things to do 😎

A couple of calls ago @handrews was making a compelling argument that in order to support SAFs, and potentially additional SIGs, we'll need to align those automations across repositories (and potentially move it to an "engineering systems" repo), so it doesn't become a nightmare to manage/use.

I'm not married to any given solution for this specific problem, but I do think this should be aligned across repositories.

What do you think?

We dropped the idea of having a common tools repo for the respec and schema publishing stuff for Arazzo, OpenAPI, and Overlays because the repos are structured differently, for example how branches are used for different versions. Can't find the issue/discussion where we documented that decision.

If all SAF/SIG repos are structured identically, a common tools repo might work for them.

One question of course would be: should the new repos use the simple Overlays approach with version files in the main branch, or the more complicated Arazzo/OpenAPI approach with version branches?

With differently structured repos, plus more or less subtle differences in the respec processing, "aligning" means "copy, paste, and adjust".

Linkspector issue UmbrellaDocs/linkspector#177 is fixed with v0.5.5 and action-linkspector uses that version.