You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2020/10/02 07:51:49 UTC

[GitHub] [arrow] jorgecarleitao commented on pull request #8324: ARROW-10156: [Rust] Added github action to label PRs for rust.

jorgecarleitao commented on pull request #8324:
URL: https://github.com/apache/arrow/pull/8324#issuecomment-702582768


   I agree @kou that `dev_cron` is not suitable atm and I though about a new flow. However, looking at the current jobs there, I think that they can all be migrated to a different `on`, since they can all be triggered by events, instead of a schedule.
   
   So, my plan was to PR a migration of that dev_cron to be triggered by events, like you suggest. Does this make sense?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org