SHACL is not run automatically anymore

[KonradHoeffner]

Maybe something changed that pushes from within other actions don't trigger branch push triggers in other actions anymore?

name: SHACL

on:
  workflow_dispatch:
  push:
    branches:
      - dist

jobs:
  shacl:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          ref: 'dist'

      - name: Build and Validate
        uses: konradhoeffner/shacl@v1
        with:
          data: all.ttl
          shacl: shacl.ttl

[KonradHoeffner]

I think we had that problem somewhere else. Anyways, it is described at https://github.com/orgs/community/discussions/37103.

[KonradHoeffner]

After some research, this is surprisingly tricky:

• a fine-grained personal access token with access to this repo would be ideal, but in the user settings one cannot create one of those
• on the other hand, in the organization account it seems impossible to create a fine-grained personal access token
• using a GitHub app is too complicated

So I see two options:

1. triggering the SHACL workflow manually
2. letting the SHACL workflow work from the master branch, not dist

Option 2 is preferable.

The SNIK ontology SHACL workflow does already work like that, by testing each Turtle file separately, but HITO only validates when all files are merged.

[KonradHoeffner]

The problematic files are:

• [ ] individual.ttl
• [ ] swp.ttl

Unfortunately they seem to depend on several other files and the -e option to designate an ontology does not change anything. Because of the large disparity between the low expected time saving for our infrequent releases and the effort of finding the best suited workaround, this will not be worked on right now but we may reopen this in the future if a better solution arises.