Skip to content

Avoid CI run when only changes files in doc/#1817

Merged
yhmtsai merged 4 commits into
developfrom
doc_norun_ci
Apr 11, 2025
Merged

Avoid CI run when only changes files in doc/#1817
yhmtsai merged 4 commits into
developfrom
doc_norun_ci

Conversation

@yhmtsai
Copy link
Copy Markdown
Member

@yhmtsai yhmtsai commented Mar 28, 2025

After #1813 , I believe we will have more PR just improving documentation.
All documentation build are handled in readthedoc, so we do not need to occupy our CI for that.
Some are still working like pre-commit check, spell check, pr label, etc without the compilation need.
Others like gitlab, osx, intel, abidiff which require compile ginkgo will not be executed when only changes the file under doc/
If some changes in other place or it is our main/develop branch, the CI still performs as usual.
gitlab ci currently does not support the ignore pattern unfortunately (related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/198688)
We need to use the opposite way to check whether others file changed or not. It definitely goes crazy if we have more conditions. (see the gitlab changes)
Github action has path_ignore which makes thing clear.

I also want to avoid mirror when it is not main/develop and no changes out of doc in github action rather than doing that in gitlab side. any comments on it?
It is done.
When use branch and path condition, both are required to be satisfied for running a job.
Also Github action does not allow two push event in one file, so I split it into two: one for the major branches, which always mirror, and the other for the rest, which only mirror when there are more than documentation changes

@yhmtsai yhmtsai added 1:ST:ready-for-review This PR is ready for review 1:ST:need-feedback The PR is somewhat ready but feedback on a blocking topic is required before a proper review. labels Mar 28, 2025
@yhmtsai yhmtsai requested review from a team and MarcelKoch March 28, 2025 16:03
@yhmtsai yhmtsai self-assigned this Mar 28, 2025
@ginkgo-bot ginkgo-bot added the reg:ci-cd This is related to the continuous integration system. label Mar 28, 2025
Copy link
Copy Markdown
Member

@pratikvn pratikvn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I am fine with mirroring only when it is main/develop. I am also fine with doing that from the github side.

Comment thread .github/workflows/bot-pr-updated.yml
@yhmtsai yhmtsai force-pushed the doc_norun_ci branch 2 times, most recently from b41bd00 to 783aedc Compare April 2, 2025 13:56
@yhmtsai yhmtsai requested a review from pratikvn April 2, 2025 13:59
@yhmtsai yhmtsai added 1:ST:skip-full-test 1:ST:no-changelog-entry Skip the wiki check for changelog update labels Apr 2, 2025
Copy link
Copy Markdown
Member

@pratikvn pratikvn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@yhmtsai yhmtsai added 1:ST:ready-to-merge This PR is ready to merge. and removed 1:ST:ready-for-review This PR is ready for review 1:ST:need-feedback The PR is somewhat ready but feedback on a blocking topic is required before a proper review. labels Apr 10, 2025
yhmtsai added 4 commits April 11, 2025 10:49
Note. Github action need to fulfill path and branch condition at the same time
Github does not support two push in the same file.
We split it into two file such that we always mirror on the major branches but only mirror when more than doc change in the other branches
@yhmtsai yhmtsai merged commit e797f4a into develop Apr 11, 2025
11 of 12 checks passed
@yhmtsai yhmtsai deleted the doc_norun_ci branch April 11, 2025 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1:ST:no-changelog-entry Skip the wiki check for changelog update 1:ST:ready-to-merge This PR is ready to merge. 1:ST:skip-full-test reg:ci-cd This is related to the continuous integration system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants