Skip to content
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

Doc: exclude post type #60

Merged
merged 5 commits into from
Jun 4, 2020
Merged

Doc: exclude post type #60

merged 5 commits into from
Jun 4, 2020

Conversation

dinhtungdu
Copy link
Contributor

@dinhtungdu dinhtungdu commented May 6, 2020

Description of the Change

Adding a section for FAQ on excluding custom post type.

This PR comes from this w.org topic: https://wordpress.org/support/topic/exclude-certain-custom-post-type

Checklist:

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my change.
  • All new and existing tests passed.

@dinhtungdu dinhtungdu requested a review from jeffpaul May 6, 2020 23:36
@dinhtungdu dinhtungdu self-assigned this May 6, 2020
@jeffpaul jeffpaul added this to the 2.4.0 milestone May 7, 2020
@jeffpaul jeffpaul added the needs:documentation This requires documentation. label May 7, 2020
Copy link
Member

@jeffpaul jeffpaul left a comment

Choose a reason for hiding this comment

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

I made a couple small copy changes, otherwise this looks good to go. Thanks for helping improve the docs and sensing this from our WordPress.org support requests!

@jeffpaul jeffpaul merged commit e8dabde into develop Jun 4, 2020
@jeffpaul jeffpaul deleted the docs/exclude-custom-post-type branch April 21, 2021 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:documentation This requires documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants