PuppetDB docs are published via the doc-* branches: - docs for Puppet 7 (`main` branch): `doc-latest` branch - docs for Puppet 6 (`6.x` branch): `doc-6.y` branch
These `doc-*` branches control what docs are published at https://puppet.com/docs/puppetdb. To publish new docs, the branches are bumped to a newer commit on their respective development branch. This is traditionally done by updating the branch locally and pushing directly. Here is an example using the `main` and `doc-latest` branches:
{code} git fetch origin git switch doc-latest git log --oneline --graph origin/main # Look at commits on main branch to pick out one for docs to publish from git reset --hard <tag-or-commit-from-the-main-branch> git push origin {code}
After a short time the changes should be live. Check https://puppet.com/docs/puppetdb and confirm that the new changes look right. You can check what documentation changed with `git diff`. Here is an example using the `main` and `doc-latest` branches: {code} git diff <previous-doc-latest-branch-head>..doc-latest -- documentation {code}
These doc-* branches control what docs are published at https://puppet.com/docs/puppetdb. To publish new docs, the doc branches are bumped to a newer commit on their respective development branch. This is traditionally done by updating the branch locally and pushing directly. Here is an example of updating the PuppetDB 7 docs by bumping the doc-latest branch:
{code} git fetch origin git switch doc-latest git log --oneline --graph origin/main # Look at commits on main branch to pick out one for docs to publish from git reset --hard <tag-or-commit-from-the-main-branch> git push origin {code}
After a short time the changes should be live. Check https://puppet.com/docs/puppetdb and confirm that the new changes look right. You can check what documentation changed with git diff. Here is an example using the main and doc-latest branches: