-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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] C++ Deque Push_front() #5362
Comments
@codecademy-docs I am a contributor from HacktoberFest and I would like to work on this issue. |
Hey @Cibiyanna26 , Is this your first contribution to Codecademy Docs? If so, we’re curious to know how you found out about contributing to Docs. Thanks & Regards, |
Yes, This is my first time contribution to Codeacademy Docs, I found about Codeacademy through hacktoberfest. |
@SaviDahegaonkar could you tell me how to run the project in our local machine ? |
Hey @Cibiyanna26 refer to this Contribution Guide, it has videos to guide you through the process of running project on your local machine and how to submit the pull request |
Hi @mamtawardhani, I have completed the work, added .push_back() in deque topic. Will raise the pr. |
Perfect, waiting for the entry 😀 |
I have one doubt, is it ok to raise a pr from my forked main branch ? |
Yes, you will have to raise a pr from the forked branch itself |
@mamtawardhani Raised the pr. |
Reason/inspiration (optional)
"We would like a new entry on the
.push_back()
term under Deque in C++. The entry should go in a new file underdocs/content/cpp/concepts/deque/terms/push-back/push-back.md
.The entry should include:
Syntax
section that provides the syntax for the conceptExample
section that provides an example demonstrating the concept in useCodebyte Example
section that provides a codebyte example demonstrating the concept in usePlease refer to the term entry template, 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: