fix a failure when dirs is empty at changes job.

[utam0k]

fix #284

[codecov-commenter]

Codecov Report

Merging #294 (23f478f) into main (5d2901e) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #294      +/-   ##
==========================================
+ Coverage   69.76%   69.78%   +0.01%     
==========================================
  Files          46       46              
  Lines        5699     5699              
==========================================
+ Hits         3976     3977       +1     
+ Misses       1723     1722       -1     

[utam0k]

• Patterns with changes in Rust code https://github.com/containers/youki/actions/runs/1223845447

[YJDoc2]

Hey, have you tested this when no code changes are there? Asking because in https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contains it states that for arrays, it checks if the element is in the array. So as needs.changes.outputs.dirs itself is an array , wouldn't

contains(needs.changes.outputs.dirs, '[]')

check if [] is an element in the dirs, and not dirs itself is an empty array? Maybe I am wrong, as I haven't worked with github actions expressions either, so if you have run this with no code changes and this works, lgtm 👍

[utam0k]

@YJDoc2 This seems to work for now. The pattern with no code changes is ci of this PR ;)

[YJDoc2]

Oh yes! I missed that 😅 All well then 👍

[YJDoc2]

Also in one of previous commits in this PR, you had made a separate job for dependencies, was there any issue with that? Or were the dependencies not sharable across jobs?

[utam0k]

Also in one of previous commits in this PR, you had made a separate job for dependencies, was there any issue with that? Or were the dependencies not sharable across jobs?

That way of writing was completely wrong and I needed to think of another way.