Thanks, havent seen any emails since rebasing to master. On Sun, Aug 2, 2020 at 5:09 AM Tobiasz Kędzierski < [email protected]> wrote:
> Hi Alex, > > After rebase on the latest master scheduled workflow should not run, > condition for scheduled job was extended to prevent situations like this. > As mentioned by Robert, you can disable gh action in case you don't need > it. > > BR > Tobiasz > > On Thu, Jul 30, 2020 at 9:18 PM Robert Burke <[email protected]> wrote: > >> You can disable GitHub actions on your own repos via the UI or via a code >> change >> >> https://github.community/t/how-can-i-disable-a-github-action/17049 >> >> On Thu, Jul 30, 2020, 12:15 PM Ahmet Altay <[email protected]> wrote: >> >>> /cc [email protected] <[email protected]> +Emily >>> Ye <[email protected]> -- this question is related to one of the >>> recent github action prs. >>> >>> On Thu, Jul 30, 2020 at 10:23 AM Alex Amato <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I received this email indicating some build was running on my fork, >>>> though I had not been doing any work on that fork for the last few weeks. >>>> >>>> I don't really need to run these builds on my fork and don't think we >>>> need to waste resources on this. Is there some way to prevent forks from >>>> doing this? >>>> >>>> I just rebased my own fork from apache beam master now. I am not sure >>>> if that will stop it or not, but it should now be up to date. >>>> >>>> ---------- Forwarded message --------- >>>> From: Alex Amato <[email protected]> >>>> Date: Wed, Jul 29, 2020 at 7:47 PM >>>> Subject: [ajamato/beam] Run failed: Build python wheels - master >>>> (9ca80ae) >>>> To: ajamato/beam <[email protected]> >>>> Cc: Ci activity <[email protected]> >>>> >>>> >>>> Run failed for master (9ca80ae) >>>> >>>> Repository: ajamato/beam >>>> Workflow: Build python wheels >>>> Duration: 29 minutes and 27.0 seconds >>>> Finished: 2020-07-30 02:47:17 UTC >>>> >>>> View results <https://github.com/ajamato/beam/actions/runs/187983527> >>>> Jobs: >>>> >>>> - build_source <https://github.com/ajamato/beam/runs/925886578> >>>> succeeded (0 annotations) >>>> - Build wheels on ubuntu-latest >>>> <https://github.com/ajamato/beam/runs/925892640> succeeded (0 >>>> annotations) >>>> - Build wheels on macos-latest >>>> <https://github.com/ajamato/beam/runs/925892647> succeeded (0 >>>> annotations) >>>> - Prepare GCS <https://github.com/ajamato/beam/runs/925892670> >>>> succeeded (0 annotations) >>>> - Upload source to GCS bucket >>>> <https://github.com/ajamato/beam/runs/925893275> failed (1 >>>> annotation) >>>> - Tag repo nightly <https://github.com/ajamato/beam/runs/925940497> >>>> succeeded (0 annotations) >>>> - Upload wheels to GCS bucket (ubuntu-latest) >>>> <https://github.com/ajamato/beam/runs/925940517> cancelled (2 >>>> annotations) >>>> - Upload wheels to GCS bucket (macos-latest) >>>> <https://github.com/ajamato/beam/runs/925940521> failed (1 >>>> annotation) >>>> - List files on Google Cloud Storage Bucket >>>> <https://github.com/ajamato/beam/runs/925941387> skipped (0 >>>> annotations) >>>> >>>> — >>>> You are receiving this because this workflow ran on your branch. >>>> Manage your GitHub Actions notifications here >>>> <https://github.com/settings/notifications>. >>>> >>>
