Try fix workflow

[PierreGtch]

No description provided.

[bruAristimunha]

This issue is different! Sensational!

If you have time, can you take look on the secret on the neurotechx organization @sylvchev? Maye someone outside of the moabb project may have updated it on neurotechx and we didn't see it.

[PierreGtch]

Yes, the idea is to have the git sha of the HEAD written somewhere in the generated HTML files so that we are sure that there is always a difference between two pushes to the gh pages repo.

[PierreGtch]

Why are we not using actions/cache/restore@v3 to get the build cache here:

moabb/.github/workflows/docs.yml

Line 112 in 29c0423

uses: actions/cache@v3

See here: https://github.com/actions/cache/blob/v3.3.3/caching-strategies.md#make-cache-read-only--reuse-cache-from-centralized-job

[PierreGtch]

Why is the cache named "Cache datasets and docs"? I don't see where we are caching the datasets

[PierreGtch]

I think we should use a "short lived cache" for the docs build: https://github.com/actions/cache/blob/v3.3.3/caching-strategies.md#creating-a-short-lived-cache

Otherwise there might be interactions between different workflow runs

[bruAristimunha]

Hey @PierreGtch!

I tried something because I wanted to see if you work. You can revert if it does not work. I gave you admin permission to access the moabb secret keys. This could help the GitHub.io deployment.

I don't have permission from the organization NeuroTechX, so we need to wait for @sylvchev

[bruAristimunha]

Suggested change

	key: docs-build-${{ github.run_id }}-${{ github.run_attempt }}
	key: docs-build

[bruAristimunha]

avoiding cache explode

[PierreGtch]

I used docs-build-${{ github.run_id }}-${{ github.run_attempt }} to have one different cache for every new CI run. Otherwise, some previously existing builds will be re-used. Is this what we want?

[sylvchev]

Usually yes, in almost all cases we want to reuse installed pip/poetry packages and downloaded datasets

[sylvchev]

Do you need new secret keys?