Hi team, I got an issue when using this keep_reports action

[Foxtel-chenfan]

Existing logic:
keep_reports action is default to 20, after the reports count over than 20, it will remove the last history, and we treat the smallest build number folder as the last history

But we have a scenario that the smallest build number is not the real last history.

Condition:

• The repo only has one project, so it's not the case which subfolder mentioned.
• We created 2 actions one is for running job by push, another is for schedule. Each has their own build number like above screenshot

Issue:
In my case, the on schedule build number #6 is the newly generated, but when next push happens, the #6 allure history report was removed as the total report count over than 20. This caused me can't access the #6 generated report anymore. May I seek for your help on how to handle my scenario?

[mgrybyk]

Hello,
I'm not sure if this action is still maintained. I may suggest using https://github.com/marketplace/actions/allure-report-with-history-per-branch. The action doesn't rely on the build number so you should not experience the issue.