Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Documentation Updates should not trigger CI tests #389

Closed
osopardo1 opened this issue Aug 28, 2024 · 0 comments · Fixed by #396
Closed

Documentation Updates should not trigger CI tests #389

osopardo1 opened this issue Aug 28, 2024 · 0 comments · Fixed by #396
Assignees
@jorgeMarin1
Labels
build type: documentation Improvements or additions to documentation

Comments

@osopardo1
Copy link
Member

Even if we change the Documentation files, the whole CI is triggered, which takes around 1h to complete.

It is better to add a policy to ignore those tests when only .md files are modified.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jorgeMarin1 jorgeMarin1

Labels
build type: documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 389: Documentation Updates should not trigger CI tests jorgeMarin1/qbeast-spark
2 participants
@osopardo1 @jorgeMarin1