Skip to content

test: cover community pack subpath semantics - #68

Open
iuyua9 wants to merge 1 commit into
botingw:mainfrom
iuyua9:test/community-pack-subpath-regressions
Open

test: cover community pack subpath semantics#68
iuyua9 wants to merge 1 commit into
botingw:mainfrom
iuyua9:test/community-pack-subpath-regressions

Conversation

@iuyua9

@iuyua9 iuyua9 commented Aug 3, 2026

Copy link
Copy Markdown

Summary

  • add integration coverage for github:user/repo[/path] community pack slugs
  • cover index path entries, subpath installation, and README/source URL rendering
  • keep the change test-only; no production behavior changes

Validation

PYTHONPATH=src pytest tests/integration/test_community_packs_subpath.py tests/integration/test_community_packs_add.py tests/integration/test_community_packs_index.py tests/integration/test_community_packs_list.py tests/integration/test_packs_status.py -o addopts=""

Result: 19 passed.

This is a focused regression suite for the existing subpath contract; no duplicate open or merged PR was found for this coverage.

Add minimal integration regression tests for the community pack
subdirectory path seam:

- parse_slug splits user/repo/sub/pack into (user, repo, subpath)
- add_pack_from_slug installs from the subdirectory, not the repo root
- community index 'path' field drives the install slug and clone target
- packs list and packs status render the README/source URL with the
  subpath embedded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants