docs
docs copied to clipboard
[Concept Entry] Python Deque Deque #4452
Description
- Added the Concept Entry Python Deque
Issue Solved
- Closes #4452
Type of Change
- Adding a new entry
Checklist
- [x ] All writings are my own.
- [x ] My entry follows the Codecademy Docs style guide.
- [x ] My changes generate no new warnings.
- [x ] I have performed a self-review of my own writing and code.
- [x ] I have checked my entry and corrected any misspellings.
- [x ] I have made corresponding changes to the documentation if needed.
- [ x] I have confirmed my changes are not being pushed from my forked
main
branch. - [ x] I have confirmed that I'm pushing from a new branch named after the changes I'm making.
- [ x] I have linked any issues that are relevant to this PR in the
Issues Solved
section.
@Aquacoder345
you've committed changes to the package.json
and yarn.lock
files. Please remove these changes.
@letsbuildanything I believe I found and delete the changes made to the package.json. To my knowledge I did not make any manual changes to the yarn.lock file, are you able to assist me with finding what changes I made to yarn.lock.
@Aquacoder345, you might be seeing these changes, possibly due to package updates made by you. I suggest reverting them back to their previous state/version, which might solve this issue. Feel free to ask if you need any further assistance. Looking forward to your response.
Hey @Aquacoder345,
I’ve reverted the changes in the yarn.lock
file. Could you please update your contribution file to ensure it aligns with Codecademy's contribution guidelines? Additionally, make sure to review and follow our style guide.
Thank you!
Thank you @letsbuildanything. I will get this resolved as soon as i possible can.
@Aquacoder345 It's been a week since the request was made. Please make the necessary changes as soon as possible. Thank you!
@letsbuildanything I am in the process of moving and will get these changes made. apology in getting these changes completed.
@Aquacoder345, please ensure you close an existing PR before opening a new one for the same issue. since you've opened a similar new PR#4759, I am closing this PR.