[ISSUE] Strategically use [skip ci] on add-and-commit workflow tasks that you don't want CI to run

[jessesimpson36]

Describe the issue:

Whenever I open up a draft PR, I add a commit, I start tailing the github actions workflow logs, and after 5 minutes around the time when helm install happens and I'm about to get some meaningful result out of the logs, all my workflow runs get cancelled and I have to tail the new workflow logs. What changed? Chart Chores gave a README.md update.

So we need a new set of unit test runs and integration test runs, all because a README.md file changed.

Actual behavior:

You stubbed your toe inside a github actions workflow.

Expected behavior:

New workflow runs are not triggered whenever a change is just a readme.md update. We can use [skip ci] in the commit message of any commit in order to skip triggering of the ci.

How to reproduce:

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

• Platform:
• Helm CLI version:
• Chart version:
• Values file:

[eamonnmoloney]

Added to the baseline epic as this is part of the reason our CI can look green even tho the ITs are failing

[hisImminence]

Added to the baseline epic as this is part of the reason our CI can look green even tho the ITs are failing

Okay! Will assign to you and move to next then 🙏