Skip to content

Conversation

@alenn97
Copy link
Contributor

@alenn97 alenn97 commented Jan 11, 2023

Description

Type of Change

  • Adding a new entry
  • Editing an existing entry (fixing a typo, bug, issues, etc)
  • Updating the documentation

Checklist

  • All writings are my own.
  • My entry follows the Codecademy Docs style guide.
  • My changes generate no new warnings.
  • I have performed a self-review of my own writing and code.
  • I have checked my entry and corrected any misspellings.
  • I have made corresponding changes to the documentation if needed.
  • I have confirmed my changes are not being pushed from my forked main branch.
  • I have confirmed that I'm pushing from a new branch named after the changes I'm making.
  • Under "Development" on the right, I have linked any issues that are relevant to this PR (write "Closes # in the "Description" above).

@CLAassistant
Copy link

CLAassistant commented Jan 11, 2023

CLA assistant check
All committers have signed the CLA.

@Dusch4593
Copy link
Contributor

Amazing! Thank you for submitting this, @alenn97 🎉

Either myself or one of my colleagues will step fourth to perform a review for this PR. After at least 2 reviews have been approved, we should be ready to merge this.

One last piece of advice I'd like to offer regarding your Docs fork: Since new changes are constantly being merged into the main branch of the base Codecademy/docs repo, this will sometimes put your fork's main branch x-commits behind:

Screen Shot 2023-01-11 at 11 48 39 AM

Before starting a new PR branch for next entry, you'll need to make sure this is caught up on GitHub, like so:

Screen Shot 2023-01-11 at 11 49 54 AM

Then, on your terminal, go back to your main branch with git checkout main and then run git pull to catch things up on the local end.

@Dusch4593 Dusch4593 added python Python entries new entry New entry or entries status: ready for next review labels Jan 11, 2023
@Dusch4593 Dusch4593 changed the title add new term entry about the help() function [New Term] Python Built-in Functions: help() Jan 11, 2023
@alenn97
Copy link
Contributor Author

alenn97 commented Jan 11, 2023

Thank you.
If the update is needed for this pull request I will do it as soon as I can.

@SSwiniarski SSwiniarski self-assigned this Jan 11, 2023
@SSwiniarski SSwiniarski added status: under review Issue or PR is currently being reviewed and removed status: ready for next review labels Jan 11, 2023
Copy link
Contributor

@SSwiniarski SSwiniarski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alenn97 I did a first review and only had a couple of comments.

Copy link
Contributor

@SSwiniarski SSwiniarski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alenn97 aside from a couple of comments about spacing, this looks ready for a second review.


```py
help(print)
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There need to be line breaks before and after code blocks

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I commit a new version with the correct spacing right now or do I have to wait for the second review?

Copy link
Contributor

@SSwiniarski SSwiniarski Jan 14, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alenn97 Go ahead and commit a new version.

```py
help()
```
Which returns as output:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There need to be line breaks before and after code blocks.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alenn97 after applying these line breaks, I would then suggest we switch the two examples in this "Example" section. So, the first example should be help() + start screen, followed by help(print) + documentation results.

@Dusch4593
Copy link
Contributor

@alenn97 I'm going to take a look for review 2️⃣ 😄

@Dusch4593 Dusch4593 self-requested a review January 14, 2023 19:35
@Dusch4593 Dusch4593 self-assigned this Jan 14, 2023
@Dusch4593 Dusch4593 added status: under review Issue or PR is currently being reviewed and removed status: ready for next review labels Jan 14, 2023
Copy link
Contributor

@Dusch4593 Dusch4593 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alenn97 left you some comments/suggestions for review 2️⃣

Let us know if you have any questions or need any assistance with implementing the feedback. 😄

```py
help()
```
Which returns as output:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alenn97 after applying these line breaks, I would then suggest we switch the two examples in this "Example" section. So, the first example should be help() + start screen, followed by help(print) + documentation results.

@Dusch4593 Dusch4593 added status: waiting for author and removed status: under review Issue or PR is currently being reviewed labels Jan 14, 2023
@SSwiniarski SSwiniarski linked an issue Jan 15, 2023 that may be closed by this pull request
3 tasks
@alenn97 alenn97 requested a review from Dusch4593 January 15, 2023 20:11
Copy link
Contributor

@Dusch4593 Dusch4593 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alenn97 This looks good to merge! I made the following edits in 1699869 before doing so:

  • Combined lines # 24 and 25 into one sentence (now just line # 24).
  • Small edits on line # 26 and # 30.
  • Removed extra spacing to get the GitHub checks to pass.

@github-actions
Copy link

👋 @alenn97
You have contributed to Codecademy Docs, and we would like to know more about you and your experience.
Please take a minute to fill out this four question survey to help us better understand Docs contributions and how we can improve the experience for you and our learners.
Thank you for your help!

@Dusch4593
Copy link
Contributor

Congratulations and thank you so much for contributing to Codecademy Docs, @alenn97! 🎊 🥳 🎉

I'm super proud of you for sticking through the whole process, from the repo setup to PR and reviews!

The new entry should now be live: https://www.codecademy.com/resources/docs/python/built-in-functions/help

Screen Shot 2023-01-17 at 12 06 38 PM

Looking forward to your next Docs contribution! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Term Entry] Python Built-in Functions: help()

4 participants