Trigger docs only when something inside the docs folder changed

[KasukabeDefenceForce]

📝 Description

Type: 🎢 infrastructure
I am trying to implement a conditional logic in the docs workflow so that the docs trigger only if there is a change in any of the files in the docs directory.

📌 Resources

Examples, notebooks, and links to useful references.

🚦 Testing

How did you test these changes?

• Testing pipeline
• Other method (describe)
• My changes can't be tested (explain why)

☑️ Checklist

• I requested two reviewers for this pull request
• I updated the documentation according to my changes
• I built the documentation by applying the build_docs label

Note: If you are not allowed to perform any of these actions, ping (@) a contributor.

[andrewfullard]

Why are the tests failing in this PR?

[atharva-2001]

Can you please include example workflows- conditions when the workflow ran successfully?

[atharva-2001]

Thanks, Abhinav, I believe the workflow will now run if there are changes in the docs folder. But someone will still be able to run it manually too using the build-docs label(without skipping), as a test?

[atharva-2001]

Why are the tests failing in this PR?

The regression cache was corrupt(size was in bytes). Deleted the cache and now it works.

[KasukabeDefenceForce]

Thanks, Abhinav, I believe the workflow will now run if there are changes in the docs folder. But someone will still be able to run it manually too using the build-docs label(without skipping), as a test?

What should be its behavior when we manually run it? If there are no changes in the docs then it should not do anything or it should run all the steps?

[andrewfullard]

With build-docs label: should always run the full docs build on PR commits
With force run in actions list: run the full docs build
With docs change: automatically run the full docs build

[KasukabeDefenceForce]

Thanks, Abhinav, I believe the workflow will now run if there are changes in the docs folder. But someone will still be able to run it manually too using the build-docs label(without skipping), as a test?

Yes, we can run it manually, by either manually running the workflow or by adding the build docs label to the PR.

[atharva-2001]

There is a merge conflict. Also, can you provide example workflow links?

[KasukabeDefenceForce]

There is a merge conflict. Also, can you provide example workflow links?

Here are the workflow links which i an on my personal forks:
DOC Change:
https://github.com/KasukabeDefenceForce/tardis/actions/runs/8940316781
NON DOC CHANGE:
https://github.com/KasukabeDefenceForce/tardis/actions/runs/8940347093
BUILD_DOCS LABEL:
https://github.com/KasukabeDefenceForce/tardis/actions/runs/8940393897