docs(README): correct deploy claim; CI builds and pushes the image only#110
Merged
Conversation
The Releasing section claimed the site is deployed automatically. CI only builds and pushes ghcr.io/encryption4all/postguard-docs:edge; the NGINX container on the production host still has to pull the new tag and restart out of band. Mirrors the wording already in docs/repos/postguard-outlook-addon.md. Closes #109
Contributor
Author
|
Rule-compliance pass found three PR-meta gaps (diff itself was already clean):
The missing PostGuard logo at the top of the README (per |
![dobby-coder[bot]](https://avatars.githubusercontent.com/in/3365457?s=60&v=4){kind=small}
Contributor
Author
There was a problem hiding this comment.
LGTM — would approve, but GitHub blocks self-review on this bot-authored PR.
Verified against .github/workflows/ci.yml: the workflow only builds and pushes the image (edge tag on main, pr-* on PRs, semver on tags) — there is no deploy step. New wording is accurate and mirrors the equivalent honest paragraph already in docs/repos/postguard-outlook-addon.md:164. Title is conventional-commit; closes #109. README-only change, build unaffected. Safe to merge.
rubenhensen
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #109. The README's Releasing section claimed the site is deployed automatically via GitHub Actions. That isn't true —
.github/workflows/ci.ymlonly builds and pushesghcr.io/encryption4all/postguard-docs:edge. The NGINX container on the production host servingdocs.postguard.eustill has to pull the newedgetag and restart out of band.Wording mirrors the equivalent honest paragraph already in
docs/repos/postguard-outlook-addon.md:164.Test plan
ci.yml(build + push only, no deploy step).README.md-only change; no source files touched, sonpm run docs:buildis unaffected.Closes #109