Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

KinsonDigital / PackageMonster Public

Notifications You must be signed in to change notification settings
Fork 2
Star 3

Code
Issues 6
Pull requests 11
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

✅Unit Testing Status Check

✅Unit Testing Status Check (main branch) #135

Sign in to view logs

Sign in to view logs

✅Unit Testing Status Check (main branch)

✅Unit Testing Status Check (main branch) #135

Summary
Jobs
- Print & Validate Run DotNet Tests Workflow
  
  Resolve Project File Path
  
  Run Unit Tests
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

11 warnings

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Execute Unit Tests: PackageMonster/GlobalUsings.cs#L5

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/GlobalUsings.cs#L6

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/GlobalUsings.cs#L7

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/GlobalUsings.cs#L8

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/Program.cs#L5

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/Program.cs#L6

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/Services/AppService.cs#L5

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/Services/ArgParsingService.cs#L5

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/Services/GitHubConsoleService.cs#L5

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Execute Unit Tests: PackageMonster/Services/IActionOutputService.cs#L5

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

PackageMonster Test Status Check / Run Unit Tests

PackageMonster Test Status Check / Run Unit Tests

succeeded Nov 7, 2024 in 26s

Loading

Re-running jobs...

You can’t perform that action at this time.