actions / actions/setup-dotnet
Multiple Package Sources
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 572
- Avg merge
- 12d 20h
- Merged PRs (30d)
- 1
Description
Description:
Opening this as per https://github.com/actions/setup-dotnet/issues/75#issuecomment-776603763.
Justification:
Configuring a package source shouldn't preclude me from consuming packages from any other sources. For example, GitHub and Azure Devops are popular for private organization packages. Whereas MyGet is often used for pre-release feeds. Then of course you have Nuget, which while people should be able to disable it, is usually the root-most fallback.
As such, multiple sources should be supported.
Are you willing to submit a PR?
Maybe?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing how this action currently configures package sources, then determine the workflow input and source-selection behavior needed for multiple feeds; done means the requested sources can coexist without preventing fallback sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100