Getting daily "Run failed: sync-files - main (2a39743)" emails after forking autowarefoundation/.github

[ghost]

Email contents:

Workflow run result:

Error occurs even though my fork is up to date with the upstream repository:

This looks to be related to some CI/CD GitHub Action that was set up for this repository (although I don't really understand what is happening).

What is the app_id that must be supplied to stop these errors from occurring and how do I supply it?

[kenji-miyake]

@LalithVipulananthan You don't have to run this workflow on your fork, so you should disable this workflow.

Or you can disable the entire GitHub Actions on your fork.

[ghost]

@kenji-miyake Thank you very much! I disabled all GitHub actions for my fork and the problem has been resolved! 😄

Is this a problem that other contributors may also experience when forking autoware repositories, or is a problem specific to the .github repo?

[kenji-miyake]

There is a related issue here. autowarefoundation/autoware.universe#319
Generally scheduled workflows are disabled when you fork it, but for some reason sometimes it will be activated. (Probably when the workflow file is updated? 🤔 )