Skip to content

chore: don't let trigger-update run on forks, as it will fail there - #5280

Open
jonasdedden wants to merge 1 commit into
lance-format:mainfrom
jonasdedden:release-timer-not-for-forks
Open

chore: don't let trigger-update run on forks, as it will fail there#5280
jonasdedden wants to merge 1 commit into
lance-format:mainfrom
jonasdedden:release-timer-not-for-forks

Conversation

@jonasdedden

Copy link
Copy Markdown
Contributor

I'm receiving loads (basically hourly or more) of error notifications on a failed CI job such as this one (https://github.com/jonasdedden/lance-ray/actions/runs/31603920768). This job can't succeed on forks, as secrets.LANCE_RELEASE_TOKEN is missing there. This PR disables it for forks.

Signed-off-by: Jonas Dedden <mail@jonas-dedden.de>
@github-actions

Copy link
Copy Markdown
Contributor

ACTION NEEDED
Lance follows the Conventional Commits specification for release automation.

The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.

For details on the error please inspect the "PR Title Check" action.

@jonasdedden jonasdedden changed the title Don't let trigger-update run on forks, as it will fail there chore: don't let trigger-update run on forks, as it will fail there Aug 12, 2026
@github-actions github-actions Bot added the chore label Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant