chocolatey / chocolatey/choco

include source name (repo name) in output of choco search

Open
#3,914 5 comments 2 reactions 0 assignees View on GitHub
0 - Triaging Enhancement
Dominant language
C#
Stars
11.5k
Forks
960
PR merge metrics
No merged PRs in 30d

Description

### Checklist

- [x] I have verified this is the correct repository for opening this issue.
- [x] I have verified no other issues exist related to my request.

### Is Your Feature Request Related To A Problem? Please describe.

we have multiple sources configured within chocolatey so when using choco search we are unable to take the output and differentiate between sources.

specifically we use `choco search --limitoutput` to get a list of packages in csv type format we have in our choco repo server (source) to determine if there are newer versions to include in a monthly update job. with only one source this is fine. now have multiple sources due to a parent company mandate so the results have multiple versions with no method to distinguish one package from the other in the output; yes, i can choco search specific sources but this is not the point and requires multiple searches to be performed which is significantly slower and requires additional code.

### Describe The Solution. Why is it needed?

adding the source name to the choco search output, or adding a parameter like `--include-source-in-output`, to include when using `--limitoutput` for a csv type format, would greatly help to narrow down needed packages.

### User Story

_No response_

### Additional Context

_No response_

### Acceptance Criteria

_No response_

### Related Issues

_No response_

Contributor guide

Open the contributing guide

Research direction

Start at the choco search command and trace how multiple configured sources are queried and how --limitoutput formats results. Review the existing source-selection behavior and output options before deciding how the source name should appear without making the requested output ambiguous. Done means one search can distinguish package results by source in its machine-readable output.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.