Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: only run benchmark workflow if running from upstream repo #18058

Conversation

rishabnayak
Copy link
Contributor

Problem

When developing on a fork, the benchmark workflow is scheduled and fails on step Check out PostHog/benchmarks-results repo

Changes

added if: github.repository == 'posthog/posthog' to existing conditional

How did you test this code?

🤞

@posthog-bot
Copy link
Contributor

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

@posthog-bot
Copy link
Contributor

This PR was closed due to lack of activity. Feel free to reopen if it's still relevant.

@posthog-bot posthog-bot closed this Nov 3, 2023
@neilkakkar neilkakkar reopened this Nov 3, 2023
@neilkakkar neilkakkar enabled auto-merge (squash) November 3, 2023 09:29
@neilkakkar
Copy link
Collaborator

thank you!

@posthog-bot posthog-bot removed the stale label Nov 6, 2023
@posthog-bot
Copy link
Contributor

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

@neilkakkar neilkakkar removed the stale label Nov 13, 2023
@neilkakkar neilkakkar changed the title only run benchmark workflow if running from upstream repo fix: only run benchmark workflow if running from upstream repo Nov 13, 2023
@neilkakkar neilkakkar merged commit f4e4d4c into PostHog:master Nov 13, 2023
71 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants