Setup CI pipeline with GitHub Actions

[Copilot]

This PR adds GitHub Actions CI workflow to improve the development process by automatically building and testing the codebase on every pull request to the develop branch.

Changes

• Added a GitHub Actions workflow file (.github/workflows/ci.yml) that:

  • Triggers on PRs to develop branch and pushes to develop
  • Builds all projects in the solution
  • Runs tests in test projects
  • Uses .NET 8.0.x SDK

• Updated README.md with:

  • CI status badge for the develop branch
  • Instructions for setting up branch protection rules
  • New "Development" section with CI pipeline details

Notes

• The CI configuration excludes Osm.Integration tests that require Windows-specific batch files (osmosis.bat), which would cause failures in the Linux CI environment
• The branch protection rules will need to be configured by a repository administrator as described in the README

Next steps (after merge)

1. Configure branch protection rules for the develop branch
2. Verify CI workflow successfully runs after merging this PR

Fixes #11.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• crl3.digicert.com
  • Triggering command: dotnet build (dns block)
• crl4.digicert.com
  • Triggering command: dotnet build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
• ocsp.digicert.com
  • Triggering command: dotnet build (dns block)
• s.symcb.com
  • Triggering command: dotnet build (dns block)
• s.symcd.com
  • Triggering command: dotnet build (dns block)
• ts-crl.ws.symantec.com
  • Triggering command: dotnet build (dns block)
• ts-ocsp.ws.symantec.com
  • Triggering command: dotnet build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[lukaskabrt]

Please fix my comments and fix failing tests.

[Copilot]

Please fix my comments and fix failing tests.

Fixed all code review issues and fixed failing tests in commit 49388ac. Tests are now passing in the CI environment.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• cdn.fwupd.org
  • Triggering command: /usr/bin/fwupdmgr refresh (dns block)
• crl3.digicert.com
  • Triggering command: dotnet test --verbosity normal (dns block)
• crl4.digicert.com
  • Triggering command: dotnet test --verbosity normal (dns block)
• ocsp.digicert.com
  • Triggering command: dotnet test --verbosity normal (dns block)
• s.symcb.com
  • Triggering command: dotnet test --verbosity normal (dns block)
• s.symcd.com
  • Triggering command: dotnet test --verbosity normal (dns block)
• ts-crl.ws.symantec.com
  • Triggering command: dotnet test --verbosity normal (dns block)
• ts-ocsp.ws.symantec.com
  • Triggering command: dotnet test --verbosity normal (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list