Target github actions better

[rob-metalinkage]

Profiles are likely to have one or more vocabularies -

processing vocabularies and processing all building blocks triggered by commits to either can be costly

can git actions be better targetted to changes in specific aspects?

[avillar]

The problem is that it's hard to anticipate the effects that a change in a bblock is going to have on the rest. A single change in a context.jsonld term can trigger 1) it's own annotated schemas and full context rebuild, 2) the same for each and every of its dependencies (both direct and indirect!). Other changes can be even more difficult to narrow down (what does a change in bblock.json entail?).

Right now, the right way to handle this is to make sure that everything works locally, and then do the push, so that the GH workflow is only triggered once.

Do you have any ideas?