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
Review and close: Content management, CLI output & shinyapps.io #964
Which of the proposed Resolved/Obsolete verdicts for the Content management, CLI output & shinyapps.io batch does the maintainer approve? Close each approved issue with its comment and close reason.
Follow-up notes for the later grooming pass: #455 is a needs-info candidate. #523's likely cause (unnormalized // in the saved server URL) is still in the code. #663, #756, #760, and #678 are related (logs and structured output) and could be planned together.
Activity
tdstein commentedon Nov 10, 2026
🤖 Resolution: The maintainer approved all 5 proposed verdicts. Each issue was closed with its drafted evidence comment from the verdict table.
rsconnect deploy apicommand torsconnect deploy flask#491,RSConnectExecutor.server_settingsthrows error ifself.clientis aPositClientobject #547rsconnect kill <content_id> [<job_id>]#505,rsconnect restart <content_id>#506,rsconnect clone <content_id>#507, error when existing content gone #542, quarto: default name should default to directory name when using index.qmd #543, Add "applications" method to rsconnect-python (already exists on R version) #654, Fetch logs if verification fails #663, Should output the content URL during deployment failure #678, Drop the "Direct Content URL" in output of deploys #683, improve output ofrsconnect details#686, support setting access type #703,rsconnect system delete cachesreports success even if it fails #746, Provide agent-friendly interface for accessing logs of content #756, feat:--jsonor something to return structured output #760Follow-up notes for the later grooming pass: #455 is a
needs-infocandidate. #523's likely cause (unnormalized//in the saved server URL) is still in the code. #663, #756, #760, and #678 are related (logs and structured output) and could be planned together.