Skip to content

Conversation

CraigThatcher
Copy link
Contributor

@CraigThatcher CraigThatcher commented Mar 8, 2022

The example given for the plan object key yearly_price_in_cents is only listing a single month cost instead of the full year. New example updated to show cost for a full year instead of a single month.

Why:

Closes [issue link]

What's being changed:

Check off the following:

  • I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
  • For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

  • This pull request impacts the contribution experience
    • I have added the 'writer impact' label
    • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

The example given for the plan object key yearly_price_in_cents is only listing a single month cost instead of the full year. New example updated to show cost for a full year instead of a single month.
@welcome
Copy link

welcome bot commented Mar 8, 2022

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 8, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Mar 8, 2022

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md Modified Original

@ramyaparimi ramyaparimi added billing Content related to billing content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team billing Content related to billing labels Mar 9, 2022
@ramyaparimi
Copy link
Contributor

@CraigThatcher
Thanks so much for opening a PR! I'll get this triaged for review ⚡

Copy link
Contributor

@ethanpalm ethanpalm left a comment

Choose a reason for hiding this comment

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

Thanks for creating this PR, @CraigThatcher! Your change looks good to go. We'll get this merged once I have the branch up to date and all checks are passing.

Thanks for taking the time to improve the GitHub docs ⚡

@ethanpalm ethanpalm added ready to merge This pull request is ready to merge and removed waiting for review Issue/PR is waiting for a writer's review labels Mar 10, 2022
@ramyaparimi ramyaparimi enabled auto-merge March 16, 2022 14:34
@ramyaparimi ramyaparimi merged commit dc7fcd8 into github:main Mar 16, 2022
@github-actions
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team ready to merge This pull request is ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants