DCO action fails on long commit history

[Yury-Fridlyand]

tim-actions/dco fails because tim-actions/get-pr-commits produced too big input for it.

An error occurred trying to start process '/home/runner/runners/2.301.1/externals/node12/bin/node' with working directory '/home/runner/work/opensearch-project-sql/opensearch-project-sql'. Argument list too long

I suppose the output of get-pr-commits should be filtered before passed to the next step.

See raw GHA logs: 2.txt

Thanks!

[Tim-Zhang]

@Yury-Fridlyand I see there are more than 80 commits in the pull request. We have not encountered such a situation so far,
and I don't think filter is a good idea, because get-pr-commits doest know what fields the consumer uses.

If you have any ideas to fix this then pull requests are welcome, thank you

[Tim-Zhang]

@Yury-Fridlyand Maybe it could be resolved by adding a filter_fields option, what do you think? could you please help to fix this?

[Yury-Fridlyand]

Hi @Tim-Zhang, thank you for replying!
It is a good idea to make a filter.
Another option I see get-pr-commits to write output into a file and make consumer actions read it. To support having multiple get-pr-commits into a CI workflow they could be distinguished by step ID. A consumer (e.g. dco step) would have ID of producer (get-pr-commits) as an optional argument.

[Tim-Zhang]

@Yury-Fridlyand That sounds good, store in files is good but should be happened optional in my opinion. Anyway the PR is welcome(I have no time to develop especially do testing recently 😃 ) , I would really appropriate it.

[Yury-Fridlyand]

I'll try, but I don't want to promise anything - I have no experience creating GHA.