Same scope, multiple registries, npm install

I have an organization that publishes scoped packages to npm for public use and internal packages with the same scope name to github packages.

When my private CI script on actions is running, it seems its failing on getting the package from github registry rather than failing and then trying NPM.

I have a package on npm named @samelogic/eslint-config but I’m getting this error:

npm ERR! 404 Not Found - GET
 - npm package "eslint-config" does not exist under owner "samelogic"

Is there a way to get around this behavior?

This is the exact issue described here for many months now: GitHub Package Registry and Npm Registry for same scoped does not work @ 2020-01-10 · GitHub