dotnet-gha-build-test

name	dotnet-gha-build-test
description	Configures GitHub Actions .NET build/test -- setup-dotnet, NuGet cache, reporting.
allowed-tools	["Read","Grep","Glob","Bash","Write","Edit"]

dotnet-gha-build-test

.NET build and test workflow patterns for GitHub Actions: actions/setup-dotnet@v4 configuration with multi-version installs and NuGet authentication, NuGet restore caching for fast CI, dotnet test with result publishing via dorny/test-reporter, code coverage upload to Codecov and Coveralls, multi-TFM matrix testing across net8.0 and net9.0, and test sharding strategies for large projects.

Version assumptions: actions/setup-dotnet@v4 for .NET 8/9/10 support. dorny/test-reporter@v1 for test result visualization. Codecov and Coveralls GitHub Apps for coverage reporting.

Scope

• setup-dotnet action configuration with multi-version installs
• NuGet restore caching for fast CI
• dotnet test with result publishing and coverage upload
• Multi-TFM matrix testing and test sharding
• NuGet authentication for private feeds in GitHub Actions

Out of scope

• Starter CI templates -- see [skill:dotnet-add-ci]
• Test architecture and strategy -- see [skill:dotnet-testing-strategy]
• Benchmark regression detection in CI -- see [skill:dotnet-ci-benchmarking]
• Publishing and deployment -- see [skill:dotnet-gha-publish] and [skill:dotnet-gha-deploy]
• Azure DevOps build/test pipelines -- see [skill:dotnet-ado-build-test]
• Reusable workflow and composite action patterns -- see [skill:dotnet-gha-patterns]

Cross-references: [skill:dotnet-add-ci] for starter build/test templates, [skill:dotnet-testing-strategy] for test architecture guidance, [skill:dotnet-ci-benchmarking] for benchmark CI integration, [skill:dotnet-artifacts-output] for artifact upload path adjustments when using centralized build output layout.

---

actions/setup-dotnet@v4 Configuration

Basic Setup

steps:
  - uses: actions/checkout@v4

  - name: Setup .NET
    uses: actions/setup-dotnet@v4
    with:
      dotnet-version: '8.0.x'

```text

### Multi-Version Install

Install multiple SDK versions for multi-TFM builds within a single job:

```yaml

- name: Setup .NET SDKs
  uses: actions/setup-dotnet@v4
  with:
    dotnet-version: |
      8.0.x
      9.0.x

```text

The first listed version becomes the default `dotnet` on PATH. All installed versions are available via `--framework`
targeting.

### NuGet Authentication for Private Feeds

Configure NuGet source authentication via `actions/setup-dotnet@v4`:

```yaml

      
   
  
     
       
  
       



    



   
   
  
     

     
   


            



        



     
   
  
     



          








    
   
  
     
          
     
   
     





      



     
   
  
     
     
     



        




                                                                            
    
                                                      
                                
         
                                       






   



  
      
   

    
   
   
  
     
     
     
     



 

               
            
             







    
   
   
  
     
     










    
   
     
   
  
     
     
       







    
   
     
   
  
     
     
       









    
   
    
   
  
     
     
     











  
    
       
      
         [, ]
         [, ]
       
    
        

         
         
        
           
         
         
        
           
                
           
           
         
          
         
         
        
           
           
           





            



    
   
  
     
    
       



               






    




  
     
    
         
    
        
        
         
         
  
     
    
       
      
           
     
    
        

         
         
        
           

           
         
          
         
         
        
           
           
           





          




  
    
       
      
         [, , ]
     
    
        

         
         
        
           

           
         





                  
         
                    
                   
                
     
                
        
                    
              
              
               
                
           
                
           

Code Navigation (Serena MCP)

Primary approach: Use Serena symbol operations for efficient code navigation:

1. Find definitions: serena_find_symbol instead of text search
2. Understand structure: serena_get_symbols_overview for file organization
3. Track references: serena_find_referencing_symbols for impact analysis
4. Precise edits: serena_replace_symbol_body for clean modifications

When to use Serena vs traditional tools:

• Use Serena: Navigation, refactoring, dependency analysis, precise edits
• Use Read/Grep: Reading full files, pattern matching, simple text operations
• Fallback: If Serena unavailable, traditional tools work fine

Example workflow:

# Instead of:
Read: src/Services/OrderService.cs
Grep: "public void ProcessOrder"

# Use:
serena_find_symbol: "OrderService/ProcessOrder"
serena_get_symbols_overview: "src/Services/OrderService.cs"