Title: The backstory about this GitHub Action:<p>I discussed with an open-source maintainer why they publish npm packages from their local machine and do not use CI&#x2F;CD pipelines.<p>They said publishing should require human intervention and want to continue using multi-factor authentication to publish to the npm registry.<p>This led to building the wait-for-secrets GitHub Action. It prints a URL in the build log and waits for secrets to be entered using a browser. Once entered, the workflow continues, and secrets can be used in future steps.<p>The latest release of &quot;eslint-plugin-react&quot; to the npm registry used a one-time password (OTP) from a GitHub Actions workflow!
<a href="https:&#x2F;&#x2F;github.com&#x2F;jsx-eslint&#x2F;eslint-plugin-react&#x2F;actions&#x2F;runs&#x2F;3498968497&#x2F;jobs&#x2F;5860126389#step:9:1" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jsx-eslint&#x2F;eslint-plugin-react&#x2F;actions&#x2F;ru...</a>
Upvote: