[CI] doc check ci is blocking bot merges

[camilamacedo86]

What broke? What's expected?

We are with an issue related to the job to check if the changes were done only on the docs and skip the other tests, see:

Therefore, we need to fix the issue OR remove this check.

Reproducing this issue

Look at the PRs sometimes it has been failing

KubeBuilder (CLI) Version

master

PROJECT version

No response

Plugin versions

No response

Other versions

No response

Extra Labels

No response

[ashutosh887]

I would like to inspect the Issue and contribute @camilamacedo86

/assign

[ashutosh887]

As far can I understand, this needs some modifications in GitHub Actions workflow?
Please guide me @camilamacedo86 @varshaprasad96

[camilamacedo86]

We need to remove the code to skip the tests when only changes on the docs were performed.
Therefore, this issue now is for we are able to re-implement / re-add the checks to skip running the tests when only docs are changed.

[Sajiyah-Salat]

i was working on one doc isssue in kubernetes other repo. And there members found same problem. if its not fixed till now. I will try to fix it in kubebuilder.

[NikhilSharmaWe]

PR which added the [CI] doc check: #2608
It was previously working fine, need to identify the changes which were in the GitHub workflow that resulted it not working as expected.

[camilamacedo86]

PR which added the [CI] doc check: #2608
It was previously working fine, need to identify the changes which were in the GitHub workflow that resulted it not working as expected.

We reverted all changes done and it is still broken.
It seems that we need to change because of some deprecations.

[Kavinjsir]

Wondering about the status of this issue? Looks like CI is working well.

[NikhilSharmaWe]

It is because the changes made for adding the [CI] doc check #2608 which were causing the blocking are now reverted.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.