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.

Sign up for GitHub

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

Jump to bottom

CI tries to release in forks #25353

Closed
luc122c opened this issue Jan 20, 2024 · 1 comment · Fixed by #25354
Closed

CI tries to release in forks #25353

luc122c opened this issue Jan 20, 2024 · 1 comment · Fixed by #25354
Labels
3.x pending triage

Comments

@luc122c
Copy link
Contributor

luc122c commented Jan 20, 2024

Environment

N/A

Reproduction

N/A

Describe the bug

When you fork the nuxt/nuxt repo, the GitHub actions are also forked. One of the CI jobs is build-release, which will fail as forks will not have permission to release nuxt packages. The solution would be to add github.repository == 'nuxt/nuxt' which would skip the job.

Additional context

No response

Logs

No response
@luc122c luc122c changed the title CI tried to release in forks CI tries to release in forks Jan 20, 2024
@luc122c luc122c mentioned this issue Jan 20, 2024
Merged
9 tasks
@luc122c
Copy link
Contributor Author

luc122c commented Jan 20, 2024 •
edited

Another solution may be to use github.repository_owner == 'nuxt' as in https://github.com/nuxt/nuxt/blob/main/.github/workflows/docs-deploy.yml#L19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.x pending triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci: only release from main repo luc122c/nuxt
1 participant
@luc122c