Clarification on the proper way to change settings when doing a fork

[sneko]

Hi,

I'm in a situation where I want to fork a repository to do a pull request and I know the PR won't be accepted within a few weeks/months. So I want to be able to use the package properly but also to let others too.

My idea is to fork the repository, try to setup the needed workflows of this repo (CircleCI in this case, but also CodeClimate...). Let's say I set up all the tools so I don't have to modify workflows files.

Now since the package is named abc and the name is already taken on the npmjs.com repository I have to use a scope like @sneko/abc. But my question is:

What's the best way to adjust settings to only reroute publishing the package to my own scope?

Because I could modify in package.json all the properties: .name, .author, .repository.url but I feel it not appropriate since my fork is not intended to replace the original one (it's just temporary).

I read some discussions on this repo and it seems I could try to play with the setting .publishConfig or try to use a file .npmrc but in all cases, it makes me adding a new commit to do so, so my pull-request to the original repo will have this content, no?

What's the best way to make this transparent? An environment variable into my CI/CD workflow so semantic-release publishes into the right scope? (if so, can someone tell me which one and what to set into?)

Thank you,

(sorry if I missed the information somewhere)

cc @pvdlg