You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remove ignored/private packages on "add a changeset if you're a maintainer" link #44
Hi, I've been really enjoying the DX of "add a changeset if you're a maintainer". But whenever a PR modifies both public and ignored/private packages, changeset/bot lists all of them in the yaml header. If we don't remove those ignored/private packages manually, this will throw
Mixed changesets that contain both ignored and not ignored packages are not allowed
Example PR: aws-amplify/amplify-ui#628. This repository has private docs and e2e packages that are ignored, but they still show up in the "add a changeset" link.
Expected Behavior
Remove ignored and/or private packages from changed packages list. This will especially help external contributors that aren't too familiar with the repo.
Hey @Andarist@emmatown! You're in the CODEOWNERS file, so tagging you in. Is this something you'd consider to be in scope, and would you be open to a PR to address the issue?
Activity
feat: ignore private or ignored packages
feat: ignore private or ignored packages for comment (#105)
scriptcoded commentedon Apr 21, 2026
Hey @Andarist @emmatown! You're in the CODEOWNERS file, so tagging you in. Is this something you'd consider to be in scope, and would you be open to a PR to address the issue?