ci: add push workflow and update README badges with package table

[snovak7]

Closes #285

Summary by Sourcery

Add a push workflow that builds the .NET solution on pushes to main and update the README to reflect the new workflow and package offerings.

Build:

• Introduce a GitHub Actions push workflow that restores and builds the .NET solution on pushes to the main branch.

Documentation:

• Update README badges to point to the new push workflow and add a NuGet packages table listing available hosting extensions.

Summary by CodeRabbit

• Documentation

  • Updated README with a NuGet packages section displaying available package information.
  • Updated build status badge reference.

• Chores

  • Added continuous integration workflow for automated builds on push events to the main branch.

[sourcery-ai]

Reviewer's Guide

Adds a new GitHub Actions workflow that builds the solution on pushes to main and updates the README to use the new workflow’s status badge and to present NuGet packages in a table with individual version badges.

Flow diagram for new GitHub Actions push workflow

flowchart TD
  A[Push to main branch] --> B[GitHub Actions Push workflow]
  B --> C[Checkout repository actions/checkout@v6]
  C --> D[Setup .NET SDK actions/setup-dotnet@v5]
  D --> E[dotnet restore --locked-mode]
  E --> F[dotnet build --configuration Release --no-restore]

Loading

File-Level Changes

Change	Details	Files
Introduce a push-based CI workflow that restores and builds the .NET solution on main branch updates.	Create a Push GitHub Actions workflow triggered on pushes to the main branch. Configure environment variables to speed up and streamline .NET CLI usage in CI. Add a job that checks out the repository without persisting credentials. Set up the .NET SDK using global.json and enable dependency caching keyed by packages.lock.json files. Add steps to restore NuGet packages in locked mode and build the solution in Release without re-restoring.	.github/workflows/push.yml
Update README badges and document all NuGet packages in a structured table.	Switch the build status badge to reference the new push workflow instead of the previous package workflow. Remove the standalone NuGet badge from the header. Add a "NuGet Packages" section with a markdown table listing each package and its corresponding NuGet version badge and link.	README.md

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#285	Create a GitHub Actions push workflow that runs on pushes (to main) and performs a .NET build-only automation (restore + build, no extra steps).	✅

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• If you want the new push.yml status badge to reflect the health of incoming changes as well, consider adding a pull_request trigger alongside push so the workflow also runs for PRs targeting main.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- If you want the new `push.yml` status badge to reflect the health of incoming changes as well, consider adding a `pull_request` trigger alongside `push` so the workflow also runs for PRs targeting `main`.

## Individual Comments

### Comment 1
<location path=".github/workflows/push.yml" line_range="35-36" />
<code_context>
+      - name: Restore .NET Packages
+        run: dotnet restore --locked-mode
+
+      - name: Build .NET Solution
+        run: dotnet build --configuration Release --no-restore
</code_context>
<issue_to_address>
**suggestion (testing):** Consider adding a test step to catch regressions on push to main

Since this runs on `main`, consider adding a `dotnet test --configuration Release --no-build` step after the build so CI verifies the test suite as well as compilation.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• .github/workflows/push.yml - New push CI workflow
• .github/workflows/pr.yml - Renamed from pr.yaml
• README.md - Updated badges and NuGet packages table

---

_{Reviewed by step-3.7-flash-20260528 · 189,358 tokens}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 03a313cb-55a1-4716-b226-f9c3329690c5

📥 Commits

Reviewing files that changed from the base of the PR and between 6cc90b8 and e87ec0f.

📒 Files selected for processing (3)

• .github/workflows/pr.yml
• .github/workflows/push.yml
• README.md

---

Walkthrough

Added a GitHub Actions push workflow for the main branch that builds the solution in Release mode with .NET SDK caching and locked dependency restoration. Updated the README to reference the new workflow in build badges and added a NuGet Packages section documenting four published packages.

Changes

Push Automation

Layer / File(s)	Summary
Push workflow configuration .github/workflows/push.yml	GitHub Actions workflow triggered on main branch pushes that checks out the repo, sets up and caches the .NET SDK using global.json, restores dependencies in locked mode, and builds the solution in Release configuration without re-restoring.
README documentation updates README.md	Build status badge updated to reference the new push workflow. New "NuGet Packages" section added with a table listing four published packages (Orleans, ServiceDefaults, Temporalio, UserSecrets) with NuGet version badge links.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

area/continuous-integration

Poem

A workflow blooms on every push,
The main branch builds without a rush.
Four packages shine in badges bright—
Automation flows, the docs unite! 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	The README badge and package table update is out of scope—issue #285 specifies only build automation, not documentation changes.	Remove the README.md changes to keep the PR focused on the issue requirement. The documentation update should be addressed in a separate PR.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes both main changes: adding a push workflow and updating README badges with a package table.
Linked Issues check	✅ Passed	The push workflow implements the core objective from issue #285 to add push automation with build-only steps, meeting the stated requirement.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 285-add-push-automation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}