-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docs to include GitHub Actions #245
Comments
Definitely! I'll add some documentation about the CI configuration on GitHub Action. The best documentation about that is currently the publishment workflow of ngx-deploy-npm. I was thinking of adding it someday. Thank you for bringing opening this issue. |
I'll leave this open issue and close it when the correspondent PR gets merged. |
@rostyk-begey This post can help you in the creation of your ci pipeline. Improve your Workflow execution time by 32% ⚡ That post results from the effort put into building the |
@rostyk-begey I marked this issue as "Good First Issue". I believe it's an excellent opportunity for new contributors, and you seem to have experience with it. My dm's are open on Twitter and Telegram if you prefer private support. |
@dianjuar Is this a package hosted on NPM or GitHub? I think line #62 asks for authentication to registry yarn. You need to add Here is an example: .yarnrc
.npmrc
|
@danielnaranjo It's hosted on NPM. The line #62 is just to verify beforehand that the NPM configuration is in place. The file generation that you are mentioning is already handled on the set-up action |
Hello there! 👋
I've been working on GitHub Actions configuration for my project and I've spent pretty much time figuring out why I'm getting npm
ENEEDAUTH
error.But after, I've found this comment in publishment.yml that helped me to solve this issue.
I think it would be really helpful to have GitHub Actions sample configuration in docs (I know there is one for CircleCI).
Or at least include that comment to CI/CD section in docs.
Besides that, I'm really grateful for this tool!
The text was updated successfully, but these errors were encountered: