6. Publishing Content

Content in the production website is updated only with changes from the main branch. You need to merge the changes in your pull request into main after the PR is approved.

A GitHub automated job (GitHub Action) runs on every merge in the main branch and publishes the updated HTML content to the production website.

  1. You should get an email notification after a reviewer approves your PR or requests more changes in the content.

    pr approved email
    Figure 1. PR approval email

  2. Navigate to the PR details page and inspect the comments from the reviewer (if any) and verify that the PR is approved. If there are changes needed, then make these changes in the same branch that you created the PR for and push the changes to GitHub. Request a re-review of the new changes from the reviewer.

  3. After your PR is approved, you should merge the PR into the main branch.

    merge request
    Figure 2. Merge PR into main branch

    Click Merge pull request to merge the PR.

  4. Verify that your PR was merged into main.

    pr merged
    Figure 3. PR merged into main branch

  5. A GitHub action should automatically run after the merge to rebuild the HTML pages for the production website. Click on the Actions tab in the GitHub repository page for the course and verify that the GitHub action was successful.

    gh actions merge
    Figure 4. GitHub actions to rebuild HTML pages

  6. It may take a few minutes for the automated job to run. Click on the latest pages and deployment run.

    gh actions deploy
    Figure 5. GitHub actions deploy to production

    The deploy task should display the link to the production website with the latest generated HTML content.

  7. Click on the link in the deploy task to view the latest rendered asciidoc content. You can also view the latest content from the home page of the GitHub repository for the course by clicking the link in the About section in the panel on the right.

    gh about link
    Figure 6. View latest production content