Skip to content

ci: Skip JavaScript job on forks#2757

Open
ppenenko wants to merge 2 commits intoAcademySoftwareFoundation:mainfrom
ppenenko:ppenenko/fix/skip-javascript-on-forks
Open

ci: Skip JavaScript job on forks#2757
ppenenko wants to merge 2 commits intoAcademySoftwareFoundation:mainfrom
ppenenko:ppenenko/fix/skip-javascript-on-forks

Conversation

@ppenenko
Copy link
Contributor

@ppenenko ppenenko commented Jan 25, 2026

The JavaScript job in the main CI workflow attempts to deploy to GitHub Pages, which fails on forks since they don't have the same Pages configuration as upstream.

E.g. https://github.com/autodesk-forks/MaterialX/actions/runs/21080475833/

This adds a condition to skip the JavaScript job on forks, matching the existing pattern used by the sdist and wheels jobs.

@jstone-lucasfilm
Copy link
Member

This is a very reasonable proposal, @ppenenko, though we'll need to provide an alternative mechanism for developers to request a deployment of the MaterialX Web Viewer in their MaterialX fork.

Maybe we could link this to extended CI builds, so that a manual trigger of the main MaterialX workflow would include a deployment of the MaterialX Web Viewer?

Other ideas here are welcome, and the goal is to provide developers with easy access to testing their proposed changes to the MaterialX Web Viewer, without impacting teams that might be restricted from enabling web deployment for all MaterialX builds.

@ppenenko
Copy link
Contributor Author

Good point @jstone-lucasfilm but I'm not sure if extended builds would succeed for most forks. Let me dig deeper into the failures.

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.

2 participants

Comments