Add arti-pack repository #91

2026-09-07T23:49:34+10:00

unkin-agent commented

2026-09-07 23:49:34 +10:00

arti-pack needs a home before its scaffold can be pushed: a Neovim plugin manager that installs plugins from tagged archives proxied through artifactapi into nvim's native package path, so editor plugins come from the same artifact store as everything else instead of direct git clones.

Add the arti-pack repository, public, squash-only on a protected main
Require the test, lint and pre-commit pipelines before merge

arti-pack needs a home before its scaffold can be pushed: a Neovim plugin manager that installs plugins from tagged archives proxied through artifactapi into nvim's native package path, so editor plugins come from the same artifact store as everything else instead of direct git clones. - Add the arti-pack repository, public, squash-only on a protected main - Require the test, lint and pre-commit pipelines before merge

unkin-agent added 1 commit 2026-09-07 23:49:34 +10:00

Add arti-pack repository

ci/woodpecker/pr/pre-commit Pipeline was successful

Details

ci/woodpecker/pr/plan Pipeline was successful

Details

d0c1f7f6bd

unkin-agent commented

2026-09-07 23:58:50 +10:00

Review: issues found.

Duplicate purpose: config/git.unkin.net/unkin/repository/vimpack.yaml (merged in #90, just prior to this PR on the same base commit) already defines a repo for the exact same thing — a Neovim plugin manager installing plugins from tagged archives via artifactapi instead of git clones. Its vimpack repo already exists on Gitea (id 220). This PR adds a second repo (arti-pack) with an effectively identical description and identical config (private/branch/merge-style/branch_protection/status_check_contexts all match vimpack.yaml verbatim).
Recommendation: reject/close this PR and use the existing vimpack repo instead, unless there is a deliberate rename/rebrand from vimpack -> arti-pack in flight — in which case this PR should instead rename/update vimpack.yaml (and the underlying repo) rather than create a parallel one.

Otherwise the PR is atomic, the diff matches its stated why, and the yaml itself is internally consistent with neighbouring repository configs (field set, branch protection, status checks). The only blocker is the duplicate-purpose repo.

Review: issues found. - Duplicate purpose: `config/git.unkin.net/unkin/repository/vimpack.yaml` (merged in #90, just prior to this PR on the same base commit) already defines a repo for the exact same thing — a Neovim plugin manager installing plugins from tagged archives via artifactapi instead of git clones. Its `vimpack` repo already exists on Gitea (id 220). This PR adds a second repo (`arti-pack`) with an effectively identical description and identical config (private/branch/merge-style/branch_protection/status_check_contexts all match vimpack.yaml verbatim). - Recommendation: reject/close this PR and use the existing `vimpack` repo instead, unless there is a deliberate rename/rebrand from vimpack -> arti-pack in flight — in which case this PR should instead rename/update `vimpack.yaml` (and the underlying repo) rather than create a parallel one. Otherwise the PR is atomic, the diff matches its stated why, and the yaml itself is internally consistent with neighbouring repository configs (field set, branch protection, status checks). The only blocker is the duplicate-purpose repo.

benvin merged commit deaa0f003d into main

2026-09-08 22:59:30 +10:00

benvin deleted branch benvin/arti-pack-repo

2026-09-08 22:59:30 +10:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: unkin/terraform-git#91