We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I would like to move the information in https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb2/Redis-connector.md into https://github.com/strongloop/loopback-connector-redis/blob/master/README.md so we can have a single source for doc for this connector.
Once we move the content into the connector README, I will copy the content of https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb2/redis-README.md into https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb2/Redis-connector.md (then delete redis-README.md from the loopback.io repo).
Then our Jenkins pipeline will ensure that the content from the README is automatically incorporated into the docs.
cc @Amir-61
The text was updated successfully, but these errors were encountered:
Not a high priority .
Sorry, something went wrong.
Closing this. Follow the issue here: https://github.com/strongloop-internal/scrum-apex/issues/51
crandmck
No branches or pull requests
I would like to move the information in https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb2/Redis-connector.md into https://github.com/strongloop/loopback-connector-redis/blob/master/README.md so we can have a single source for doc for this connector.
Once we move the content into the connector README, I will copy the content of https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb2/redis-README.md into https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb2/Redis-connector.md (then delete redis-README.md from the loopback.io repo).
Then our Jenkins pipeline will ensure that the content from the README is automatically incorporated into the docs.
cc @Amir-61
The text was updated successfully, but these errors were encountered: