Skip to content

Migrate to standard .NET NuGet packaging workflow#94

Merged
jacqueskang merged 5 commits intomainfrom
feat/ci-refactor
Dec 20, 2025
Merged

Migrate to standard .NET NuGet packaging workflow#94
jacqueskang merged 5 commits intomainfrom
feat/ci-refactor

Conversation

@jacqueskang
Copy link
Copy Markdown
Owner

  • Replace custom version.yml with Directory.Build.props (standard approach)
  • Update version to 1.2.0 in Directory.Build.props
  • Refactor CI workflow to read version from Directory.Build.props
  • Create new release workflow triggered by git tags (v*..)
  • Simplify PR validation workflow to standard practices
  • Update all workflows to use .NET 10.0.x

Changes:

  • CI: Publishes pre-release packages (1.2.0-ci.N) on develop branch
  • Release: Publishes production packages (1.2.0) on git tags
  • PR: Build and test validation without version enforcement

- Replace custom version.yml with Directory.Build.props (standard approach)
- Update version to 1.2.0 in Directory.Build.props
- Refactor CI workflow to read version from Directory.Build.props
- Create new release workflow triggered by git tags (v*.*.*)
- Simplify PR validation workflow to standard practices
- Update all workflows to use .NET 10.0.x

Changes:
- CI: Publishes pre-release packages (1.2.0-ci.N) on develop branch
- Release: Publishes production packages (1.2.0) on git tags
- PR: Build and test validation without version enforcement
- Generate .trx files with --logger flag
- Upload test results in PR, CI, and release workflows
- Display test results directly in PR checks
- Show pass/fail summary and failed test details
- Add to PR validation, CI, and release workflows
- Collect code coverage with XPlat Code Coverage
- Generate coverage summary report
- Post coverage results as PR comment with badge
- Add coverage thresholds (60% warning, 80% good)
- Create comprehensive CONTRIBUTING.md
- Document development workflow and setup
- Add code guidelines and testing requirements
- Explain PR process and commit conventions
- Include release process for maintainers
- Add contributing section to README
@github-actions
Copy link
Copy Markdown

Code Coverage

Package Line Rate Branch Rate Health
JKang.EventSourcing.Options 20% 100%
JKang.EventSourcing.TestingFixtures 0% 0%
JKang.EventSourcing.Abstractions 4% 2%
JKang.EventSourcing.Persistence.DynamoDB 4% 1%
JKang.EventSourcing.Persistence.Caching 0% 0%
JKang.EventSourcing 92% 75%
JKang.EventSourcing.TestingFixtures 69% 70%
JKang.EventSourcing.Abstractions 68% 50%
JKang.EventSourcing.Persistence.Caching 0% 0%
JKang.EventSourcing.Options 20% 100%
JKang.EventSourcing.TestingFixtures 0% 0%
JKang.EventSourcing.Abstractions 4% 2%
JKang.EventSourcing.Persistence.DynamoDB 4% 1%
JKang.EventSourcing.Persistence.Caching 0% 0%
JKang.EventSourcing 92% 75%
JKang.EventSourcing.TestingFixtures 69% 70%
JKang.EventSourcing.Abstractions 68% 50%
JKang.EventSourcing.Persistence.Caching 0% 0%
Summary 30% (318 / 1428) 25% (88 / 496)

@jacqueskang jacqueskang merged commit 133bf0c into main Dec 20, 2025
2 checks passed
@jacqueskang jacqueskang deleted the feat/ci-refactor branch December 20, 2025 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant