Could you make it run on every push and pull request? I don't think running it an extra time should be a problem.

It now runs on every push and pull request。Maybe I didn’t understand what you meant。

I meant to change it to on: [push, pull_request], but it's not that important. There's a bigger problem with permissions , which means that the directory file is not updated as the workflow runs:

Do you know what the problem might be and how can I grant those permissions?

I meant to change it to on: [push, pull_request], but it's not that important. There's a bigger problem with permissions , which means that the directory file is not updated as the workflow runs: Do you know what the problem might be and how can I grant those permissions?

There are two way to grant those permissions. One is to change the settings of the repository(In my fork repository,I change the Workflow permissions to Read and write permissions, and it works), see Managing GitHub Actions settings for a repository,the other is use permissions key to grant permissions,see Assigning permissions to jobs. By the way, if change the multipie events to on: [push, pull_request] then we can not configure a workflow to run based on what file paths are changed. see Using activity types and filters with multiple events

I've checked logs of the last run, and it didn't work, even though an updated DIRECTORY was committed somehow.
In the repo settings actions are allowed to write

Could you add override of permissions in this job? Like that, maybe more permissions are needed than is on the screenshot

I've checked logs of the last run, and it didn't work, even though an updated DIRECTORY was committed somehow. In the repo settings actions are allowed to write Could you add override of permissions in this job? Like that, maybe more permissions are needed than is on the screenshot

I found that the permissions key only worked on my forked repository, so need you selected the Send write tokens to workflows from pull requests option in the GitHub Actions settings at Managing GitHub Actions settings for a repository.
.
And I have added override of permissions in this job, only need a contents: write permission for a commit operation. This workflow only update the directory info of java files, so I removed some unnecessary paths filter. In case of this pull request wont trigger the workflow after remove some paths filter, I add a workflow_dispatch key to manually running this workflow.these all worked on my forked repository.

The "updated DIRECTORY" commit was the workflow run on my forked repository, then the git actions auto commit and push to this pull request, I have reseted the commit.