Repository navigation
fix(ci): run workflows on meta/docusaurus after the repository move (AI-assisted) - #12817
Merged
Merged
Conversation
…AI-assisted) The Argos, CodeQL, Continuous Releases and Publish jobs were guarded on `github.repository == 'facebook/docusaurus'` (PR #12078 to skip them on forks), so they have been skipped since the repository moved to meta/docusaurus. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
⚡️ Lighthouse report for the deploy preview of this PR
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
#12078 guarded some workflow jobs with
github.repository == 'facebook/docusaurus'so that forks don't run them. Since the repository moved tometa/docusaurus, these guards skip the jobs on our own repository too:publish.ymlmain: the last one is4.0.0-canary-7002, 4 pushes skipped sinceargos.ymlArgoslabelcontinuous-releases.ymlcodeql-analysis.ymlThis PR only updates the repository name, keeping the fork protection.
Merging this PR will trigger a canary release (
publish.ymlis in its ownpathsfilter). If it fails to authenticate, the npm Trusted Publishing configuration of the@docusaurus/*packages probably still referencesfacebook/docusaurusand needs to be updated on npmjs.com.Test Plan
CI: the Argos, CodeQL and Continuous Releases jobs run on this PR instead of being skipped.
The other
facebook/docusaurusmentions in.github/andadmin/are links, which GitHub redirects: they don't gate any behavior.Test links
Deploy preview: https://deploy-preview-12817--docusaurus-2.netlify.app/
Related issues/PRs
🤖 Generated with Claude Code (AI-assisted)
Summary by CodeRabbit