Pavel Lobashov

By the name of folders and it's size - seems this is ONLYOFFICE CommunityServer issue, not DocumentServer issue, so I've moving this issue to correct repo

Moved this issue to CommunityServer repo, since problem is not for Docker image

> what do you mean by: "contact our ***@***.*** to discuss this particular case"? I think your mail client filtering our messages, please open github and see correct responce there...

I can share the whole repo, one of my several https://github.com/ONLYOFFICE-QA/onlyoffice_s3_wrapper/blob/master/.github/workflows/ruby.yml I'm surprise that I'm only one reporting this, I've checked issues at Dependabot and Github Actions daily and today...

@jurre > Do you have those secrets set up as both Dependabot secrets and Actions secrets? No, where was never Dependabot specific secrets configures, as I mention earlier I've triggered...

@mkrakowitzer > Actions triggered by dependabot would fail as it did not have access to secrets, and then someone from the team could retrigger them and they would now pass...

@jurre Ok thanks, I think tomorrow morning there will be some new PRs from dependabot and I'll leave this open for you to investigate

And an example that I've promised So [this is actions](https://github.com/ONLYOFFICE-QA/onlyoffice_s3_wrapper/runs/7645287788?check_suite_focus=true) run which was created by dependabot, I've not touched anything in it It shows empty secrets:  And [this one](https://github.com/ONLYOFFICE-QA/onlyoffice_s3_wrapper/runs/7646666230?check_suite_focus=true)...

> but a while ago this was changed to reuse the permissions of the original actor, but there might have been a regression for a while where this didn't work...

Ok if this was intentional and announced I think we can close this issue, personally I've adapted all my Actions to call dependabot secrets, so this is not a problem...