Describe the bug
Hey @davemlz! I was just updating my eemont fork and noticed it was ahead of the main fork by 60 commits just from automated STAC updates. It looks like the cron job workflows that are set up for eemont run independently on forks, which leads to a bunch of redundant commits. This isn't really a bug and doesn't actually cause any problems, but it does add some clutter to the commit history and eat some resources, so I thought I'd bring it to your attention in case you weren't aware :)
Describe the bug Hey @davemlz! I was just updating my
eemont
fork and noticed it was ahead of the main fork by 60 commits just from automated STAC updates. It looks like the cron job workflows that are set up foreemont
run independently on forks, which leads to a bunch of redundant commits. This isn't really a bug and doesn't actually cause any problems, but it does add some clutter to the commit history and eat some resources, so I thought I'd bring it to your attention in case you weren't aware :)Additional context I think this could be fixed by adding
if: github.repository_owner == 'davemlz'
to each of the workflow jobs. Here's a discussion of how another project fixed this and an example workflow.