docs: add a "pack a Pro artifact" how-to - #1144
Conversation
Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
There was a problem hiding this comment.
Pull request overview
Adds a new how-to guide describing how to pack a Pro-compliant artifact using Ubuntu Pro services, integrating it into the documentation navigation and release notes for Craft Application.
Changes:
- Adds a new how-to entry point page (
docs/how-to/pack-a-pro-artifact.rst) that includes shared/common content. - Introduces the shared how-to content under
docs/common/.../pack-a-pro-artifact.rstand wires it into Sphinx’s build configuration. - Updates the how-to toctree and changelog to surface the new guide.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/reference/changelog.rst | Adds a changelog entry referencing the new how-to guide. |
| docs/how-to/pack-a-pro-artifact.rst | New how-to wrapper that defines substitutions and includes the shared content. |
| docs/how-to/index.rst | Adds the new how-to page to the how-to guides toctree. |
| docs/conf.py | Excludes the new shared/common how-to source from direct processing, consistent with other common docs. |
| docs/common/craft-application/how-to-guides/pack-a-pro-artifact.rst | Adds the shared how-to content describing Ubuntu Pro-enabled packing. |
5ad08ca to
9f34722
Compare
Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
9f34722 to
b89d5ad
Compare
|
Test failures fixed in #1146 |
| .. meta:: | ||
| :description: Pack |an-artifact| that contains extended security patches or meets regulatory compliance needs, powered by Ubuntu Pro. |
There was a problem hiding this comment.
Required:
The advanced substitutions extension doesn't work for meta, unfortunately, so we'll need to move this into the destination page. It's better that way, since there will be many instances where we need to customise it.
| Follow this guide to pack |an-artifact| that contains extended security patches or meets | ||
| regulatory compliance needs. | ||
|
|
||
| .. Split point for downstream docs: Prerequisites onward |
There was a problem hiding this comment.
There are a few places in other docs where we use:
| .. Split point for downstream docs: Prerequisites onward | |
| .. Begin prerequisites |
It's a little bit easier to cite in the include options.
There was a problem hiding this comment.
I followed this method but tweaked it slightly to accomodate the feedback in the downstream PR in snapcraft
| Documentation | ||
| ============= | ||
|
|
||
| - Add a :ref:`how-to-pack-a-pro-artifact` how-to document. |
There was a problem hiding this comment.
| - Add a :ref:`how-to-pack-a-pro-artifact` how-to document. | |
| - Add a :ref:`how-to-pack-a-pro-artifact` how-to guide. |
Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
make lint && make test?docs/reference/changelog.rst)?Adds a pack a Pro artifact how-to document.
The first commit migrates the Rockcraft doc verbatim, the second commit makes it generic.
Used downstream in canonical/snapcraft#6367.
(CRAFT-5237)