Maintenance: add check to skip analytics workflow on forks

[dreamorosi]

Summary

The repo has a scheduled workflow that is used to send analytics to a backend that we use to aggregate repository events. This workflow should run only on the main repo and should not run on forks.

Why is this needed?

Because currently the workflow produces a lot of failed workflow notifications whenever the repo is forked.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.