Support registration manual NuGet source to NuGet.Config

Open
#415 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 7 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, typescript
Domain
devops, tooling

Research direction

Start by reviewing the setup-dotnet action inputs and the workflow steps shown in the issue, with attention to how NuGet.Config and the dotnet nuget commands are currently handled. Done should provide a defined way to register a manual private NuGet source without repeated add/remove steps across workflows, but the input design still needs maintainer guidance.

Written by the indexing model from the issue text.

Description

feature request needs eyes

Description:
Support registration manual NuGet source to NuGet.Config

Justification:
When we uses private NuGet repository like nexus, We need to configure our source to NuGet.Config.

I'm currently using with these code, But It is too long and scattered in many workflows.

- name: Add NuGet source (Private Nexus)
  id: add-nuget-source
  run: |
    dotnet nuget remove source Nexus | true
    dotnet nuget add source ${{ secrets.PRIVATE_NUGET_SOURCE }} \
      --name Nexus \
      --username ${{ secrets.PRIVATE_AGENT_NEXUS_USERNAME }} \
      --password ${{ secrets.PRIVATE_AGENT_NEXUS_PASSWORD }} \
      --store-password-in-clear-text

Also, we need to remove this configure with these code when using ghcr.

- name: Remove NuGet source (Private Nexus)
  if: ${{ always() && steps.add-nuget-source.conclusion == 'success' }}
  run: dotnet nuget remove source Nexus | true

Are you willing to submit a PR?
Yes, I'm interested in. But I need a help.
I don't know nice way to resolve these many arguments. Some idea please

Dominant language
TypeScript
Stars
1.2k
Forks
579
Avg merge
6d 4h
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/setup-dotnet

All issues in actions/setup-dotnet

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.