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
[Term Entry] Python Plotly .line() #4556
Comments
I am interested in taking this issue on. |
Hey @Jesuscg25, you're assigned. In addition to the documents linked in the description, please also look at our Contribution Guide if you haven't already. After creating a PR, the maintainer(s) (with the collaborator label) will add comments/suggestions to address any revisions before approval. Is this your first contribution to Codecademy Docs? If so, we're curious to know how you found out about contributing to Docs. |
Nice to meet you! Yes, it is my first time contributing to Codecademy Docs, and that's because I'm currently doing the Git & GitHub course on CodeCademy and one part of the training is contributing to the repo. |
Hey @Jesuscg25 Please re-review the path once, it has been updated. Thanks! |
Hey @mamtawardhani, my apologies, what is left to do here? |
Hey @Jesuscg25, the path of the file has been updated in the description, do take a look at the path needed for the file, before submitting the Pull Request :) |
Hi @mamtawardhani I guess the path is wrong because the description indicates: |
Hey @Jesuscg25, the current path is |
Thank you for explaining @Sriparno08! |
Reason/inspiration (optional)
We would like a new term entry in the
Data Visualization
concept for Plotly:.line()
. The entry should go in a new file underdocs/content/plotly/concepts/express/terms/line/line.md
The entry should describe the term and how it is used. Also include:
Please refer to the entry templates, content standards, and markdown style guide when working on the PR for this issue.
Entry Type (select all that apply)
New Term for Existing Concept Entry
Code of Conduct
For Maintainers
The text was updated successfully, but these errors were encountered: