feat(.github): Create generate-openapi-code-from-typespec

[creatorrr]

Important

Add GitHub Actions workflow to generate OpenAPI code from TypeSpec, with environment setup and caching.

• Workflow:
  • New GitHub Actions workflow generate-openapi-code-from-typespec added.
  • Triggers on pull_request and push events.
• Environment Setup:
  • Uses actions/setup-python@v5 to set Python 3.12.
  • Uses actions/setup-node@v4 to set up Node.js with npm caching.
  • Configures Poetry with snok/install-poetry@v1 and sets virtualenvs in-project.
• Caching:
  • Caches Poetry virtualenv in agents-api/.venv using actions/cache@v4.
• Code Generation:
  • Runs scripts/generate_openapi_code.sh to generate OpenAPI code.

^{This description was created by for 25acd5b. It will automatically update as commits are pushed.}

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 25acd5b in 31 seconds

More details

• Looked at 62 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. .github/workflows/generate-openapi-code-from-typespec:5

• Draft comment:
  Consider uncommenting and using the 'paths' filter to trigger the workflow only for changes in relevant directories, such as 'typespec/**'.
• Reason this comment was not posted:
  Comment was on unchanged code.

2. .github/workflows/generate-openapi-code-from-typespec:25

• Draft comment:
  Using 'latest' for node-version can lead to unexpected issues. Consider specifying a specific version or a major version range.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  Using 'latest' for node-version can indeed lead to unexpected issues if a new version of Node.js introduces breaking changes. Specifying a specific version or a major version range can provide more stability. This is a valid concern and suggests a clear code change that could improve the workflow's reliability.
  The comment might be seen as speculative since it assumes potential issues without evidence of them occurring. However, it is a common best practice to avoid using 'latest' for dependencies in CI/CD workflows.
  While the comment is somewhat speculative, it is grounded in a common best practice that can prevent future issues, making it a valid suggestion for improvement.
  The comment is valid as it suggests a best practice to prevent potential issues with using 'latest' for node-version. It should be kept.

Workflow ID: wflow_6Lgpe21cyAzBIKBS

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.