Skip to content

Research: which Content management, CLI output & shinyapps.io issues are resolved or obsolete? #963

Closed

Description

@tdstein

Question

For each open issue in the Content management, CLI output & shinyapps.io batch, is it already resolved, obsolete, still valid, or unclear? Find the evidence and propose a closing comment for each one marked resolved or obsolete.

Issues (27): #332, #357, #430, #439, #455, #462, #465, #474, #481, #491, #494, #505, #506, #507, #523, #542, #543, #547, #654, #663, #678, #683, #686, #703, #746, #756, #760

Output: a verdict table on branch research/groom-content with these columns: issue, verdict, evidence (PR/commit/code ref/CLI output), proposed close reason (completed / not planned / duplicate-of), and draft 🤖 closing comment. Follow the verdict rules in the map's Notes.

Activity

  1. tdstein commented on Nov 10, 2026

    @tdstein
    CollaboratorAuthor

    🤖 Research done. Verdict table and draft closing comments: https://github.com/posit-dev/rsconnect-python/blob/research/groom-content/research/groom-content.md

    #663, #756, #760, and #678 are related, but none duplicates another. No backlog issues were changed. They're ready for review in #964.

  2. self-assigned this
    on Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions