← Back to issue list

docs: migrate kde neon extensions

View original Github issue

Metadata

Project
snapcraft
Number
#5220
Type
pull request
State
merged
Author
medubelko
Labels
—
Created
Updated
Closed

Current evaluation

Docs-only PR migrating the KDE Neon extension reference to the new docs layout was merged into main as commit befd4e8f2 on 2025-01-31, after rebasing onto #5212.

Resolution: closed resolved

Reason: The PR was approved by 2 reviewers and merged by mr-cal on 2025-01-31 as commit befd4e8f2 ("docs: migrate kde neon extensions (#5220)"), adding docs/reference/extensions/kde-neon-extensions.rst (+567 lines, 4 files).

Evaluated by: mr-cal-bot

No scores available.

Issue body

- [x] Have you followed the [guidelines for contributing](https://github.com/canonical/snapcraft/blob/main/CONTRIBUTING.md)? - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [x] Have you successfully run `tox run -m lint`? - [ ] Have you successfully run `tox run -e test-py310`? (supported versions: `py39`, `py310`, `py311`, `py312`) ----- For review, please focus on `docs/reference/extensions/kde-neon-extensions.rst`. The other files will be merged through another PR.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Docs-only PR migrating the KDE Neon extension reference to the new docs layout was merged into main as commit befd4e8f2 on 2025-01-31, after rebasing onto #5212.
stealth/space-bunny-alpha — closed resolved PR #5220 merged to main as commit befd4e8f2, migrating the KDE Neon extensions docs to the new Sphinx structure (docs/reference/extensions/kde-neon-extensions.rst), rebased after #5212.
stealth/space-bunny-alpha — closed resolved Docs-only PR migrating the KDE Neon extension reference to the new docs layout. Merged to main as commit befd4e8f2 ("docs: migrate kde neon extensions (#5220)") on 2025-01-31 after rebase onto #5212.
stealth/space-bunny-alpha — closed resolved Merged the KDE Neon extensions documentation migration in PR #5220 after rebasing on #5212; reviewers reported the relevant tests passing.
qwen/qwen3.6-35b-a3b — — Merged documentation migration for KDE Neon extensions. Approved by two reviewers, rebased, and merged after passing CI checks and code coverage requirements.
qwen3.6-35b-a3b-mtp-q6 — — Merged documentation update migrating KDE Neon extensions. After rebasing and passing all relevant tests, a maintainer approved and merged the changes.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/snapcraft#5212 (confidence 90%)

    Maintainer noted the branch needed a rebase after #5212 (commit a30134d50), the companion env-injector/GNOME docs migration merged just before this one.

  • Related To: canonical/snapcraft#5226 (confidence 80%)

    Sibling docs migration (flutter extension, commit fc6c99365) from the same docs migration effort.

  • Related To: canonical/snapcraft#5227 (confidence 80%)

    Sibling docs migration (ros 2 extensions, commit 7ccefeabb) from the same effort.

  • Related To: canonical/snapcraft#5232 (confidence 80%)

    Sibling docs migration (ros 1 extensions, commit 47b0d37f1) from the same effort.

Related issues

Issue Project State Summary Similarity
#5228 docs(extensions/kde-neon): change reference to use upstream repository snapcraft open Docs task: repoint the KDE Neon 6 example project-file link in docs/reference/extensions/kde-neon-extensions.rst from lengau's keysmith fork (invent.kde.org/alexlowe/keysmith/.../snapcraft.yaml) to the upstream KDE repo
76%
#5275 docs: update build-environment for the kde-neon and kde-neon-6 extensions snapcraft open Triaged documentation task remains open: the KDE neon extension reference still shows one build environment, although the code supports distinct core22 and core24 environments; PR #6456 was closed unmerged.
75%
#4060 extensions: fix neon-extension issues for core22 snapcraft merged Merged PR #4060 as commit bef32e264, fixing KDE Neon extension compatibility with core22 by restoring the command chain, removing bindtextdomain, and updating SDK matching, part names, and tests.
73%