comaniac opened a new issue #10467: URL: https://github.com/apache/tvm/issues/10467
Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat: Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed. ### Expected behavior The forked repo should not trigger Github action workflows. ### Actual behavior The scheduled workflows, ping reviewer and update last-success branch, are triggered every day on my forked repo. This results in two annoying facts: 1) a last-success branch has been created on my forked repo, and 2) I might receive an email about execution failures. ### Environment N/A ### Steps to reproduce Any forked repo with up-to-date main branch should experience this. Here is mine: https://github.com/comaniac/tvm/actions What I did in other repos is to add a guard to make sure certain workflows (e.g., all scheduled ones) only execute on the upstream repo. Something like: ``` job_test: if: github.repository == 'my-account/repo-name' # e.g., apache/tvm runs-on: ubuntu-latest steps: ``` cc @driazati @areusch -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
