-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix: npm readme #136
fix: npm readme #136
Conversation
Even though this is just a symbolic link, do we need to have the same file content twice in the repo? |
That would work for me too. I'll work on that. |
@francardoso93 changes made |
@@ -65,6 +65,7 @@ jobs: | |||
run: | | |||
cd npm | |||
./publish.sh | |||
ln ../README.md README.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to run before the publish.sh
script
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, you need to remove the existing README.md to avoid conflict
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true.
Currently the symlinks are being created both on commited files AND dynamically through workflow. Now they should go with only one of these approaches |
@francardoso93 changes made. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR creates a symbolic link to README.md in the
npm
folder so the same readme is displayed in GitHub and NPM.To test: clone this branch and see if the npm/README.md file is populated. We also will need to check the next release to see if the README will be populated in the NPM website.
Closes #137