Reviewing Learn Content Errors

When someone submits a content error report that you can immediately action:

  1. Reply to them using the “ERROR REPORT: Thank you” saved reply and modify it to be as specific as you need for the situation.
  2. Mark it as “Closed”.

When someone submits a content error report that requires further investigation:

  1. Reply to them using the “ERROR REPORT: Thank you – ERROR LOGGED IN GITHUBGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/” saved reply and modify it to be as specific as you need for the situation.
  2. Mark it as “Pending”.
  3. Log an issue for it on the team GitHub repository.
    1. Create a new issue on GitHub, using the Content Error Report Template.
    2. Add the ticket number to the issue title. It should look like: Learn WordPress Content Error Report: Ticket # [Insert Number]
    3. Fill out the “Error Description” in the GitHub issue body.
    4. Press “Submit new issue”.
    5. If you have validated the error, or are able to propose a fix, feel free to tick the corresponding items off of the “Error Report Checklist” and leave additional comments on the GitHub thread.

Last updated: