updated gitVersion usage + net8

[bradychristensen23]

• Fixes Update GitVersion Usage In Build & .NET 8 #42

Summary by CodeRabbit

• New Features

  • Updated the GitVersion setup process for improved maintainability and clarity in CI/CD workflows.
  • Enhanced versioning configuration for branches, allowing more control over version increments based on commit tagging.
  • Upgraded the target framework of the application to .NET 8, potentially improving performance and security.

• Bug Fixes

  • Upgraded GitVersion execution action to a newer version, ensuring better functionality and bug fixes.

[coderabbitai]

Walkthrough

This update enhances the CI/CD workflows and project configuration for a .NET application by adopting the latest GitVersion setup and transitioning to .NET 8. Key changes include replacing the previous method of GitVersion installation with a standardized action, refining versioning strategies in GitVersion.yml, and updating the target framework in the project file. These modifications improve maintainability, functionality, and alignment with current best practices.

Changes

File	Change Summary
.github/workflows/ci-build.yml	Updated GitVersion setup and execution actions to v3.0.0; improved maintainability and compatibility.
.github/workflows/release-build.yml	Similar updates as in ci-build.yml; standardized action usage for GitVersion installation.
GitVersion.yml	Changed keys from tag to label, added prevent-increment under develop, and renamed patterns for consistency.
src/GitHubCostVisualizer.Web/GitHubCostVisualizer.Web.csproj	Updated target framework from net6.0 to net8.0 for enhanced performance and compatibility.

Assessment against linked issues

Objective	Addressed	Explanation
Change tag to label and tag-number-pattern to label-number-pattern (42)	✅
Add prevent-increment to develop branch (42)	✅
Update GitVersion installation method across all workflows (42)	✅
Update project to target .NET 8 (42)	✅

Poem

🐰 In the meadow where code does bloom,
New versions leap, dispelling gloom.
Labels now dance on branches so bright,
With GitVersion's grace, we take flight!
.NET 8 shines, a nimble delight,
Hopping through changes, all feels just right! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c071d4 and 413b191.

Files selected for processing (4)

• .github/workflows/ci-build.yml (1 hunks)
• .github/workflows/release-build.yml (1 hunks)
• GitVersion.yml (1 hunks)
• src/GitHubCostVisualizer.Web/GitHubCostVisualizer.Web.csproj (1 hunks)

Additional comments not posted (5)

src/GitHubCostVisualizer.Web/GitHubCostVisualizer.Web.csproj (1)

4-4: Verify compatibility with .NET 8.

The target framework has been updated to .NET 8. Ensure that all dependencies and libraries used in the project are compatible with .NET 8 to prevent runtime issues.

GitVersion.yml (2)

5-5: Changes to label terminology are approved.

The updates from tag to label and tag-number-pattern to label-number-pattern align with the latest GitVersion conventions. These changes improve clarity and consistency in versioning.

Also applies to: 12-13

---

7-8: Ensure understanding of the prevent-increment rule.

The prevent-increment rule for the develop branch prevents version increments when the current commit is tagged. This enhances control over versioning during development.

.github/workflows/ci-build.yml (1)

29-31: GitVersion setup and execution updates are approved.

The transition to using gittools/actions/gitversion/setup@v3.0.0 and execute@v3.0.0 standardizes the installation process and aligns with updated practices. Ensure compatibility with the new actions.

Also applies to: 35-35

.github/workflows/release-build.yml (1)

27-29: GitVersion setup and execution updates are approved.

The update to gittools/actions/gitversion/setup@v3.0.0 and execute@v3.0.0 enhances maintainability and aligns with current best practices. Verify compatibility with the new actions.

Also applies to: 33-33