openai/openai-dotnet
Publicmirrored from https://github.com/openai/openai-dotnetAvailable
.github/workflows.md
28lines · modecode
| 1 | The workflows in this repository try to follow existing, basic samples with little customization. |
| 2 | |
| 3 | ## main.yml |
| 4 | We use a standard dotnet build/test/pack workflow |
| 5 | https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-net |
| 6 | |
| 7 | - Build the solution using the dotnet cli |
| 8 | - Strong name the assemblies using a key stored in the repository |
| 9 | https://github.com/dotnet/runtime/blob/main/docs/project/strong-name-signing.md |
| 10 | - Test the built libraries |
| 11 | - In a PR run, only local tests are run. |
| 12 | - In a CI run, live tests are run using a repository secret containing an OpenAI token |
| 13 | https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions |
| 14 | - Package the built libraries |
| 15 | - Publish the package to a GitHub NuGet registry |
| 16 | https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry |
| 17 | - Publish a single build artifact containing test results and a nuget package |
| 18 | |
| 19 | ## release.yml |
| 20 | Releases are triggered by publishing a release in the GitHub repository. The release workflow will: |
| 21 | |
| 22 | - Build the solution using the dotnet cli |
| 23 | - Strong name the assemblies using a key stored in the repository |
| 24 | - Test the built libraries |
| 25 | - Live tests are run using a repository secret containing an OpenAI token |
| 26 | - Package the built libraries |
| 27 | - Publish the package to public NuGet registry |
| 28 | - Publish a single build artifact containing test results and a nuget package |
| 29 | |