-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4brunu feature/swift6b #19641
4brunu feature/swift6b #19641
Conversation
…nerator into 4brunu-feature/swift6b
https://github.com/OpenAPITools/openapi-generator/actions/runs/10982696444/job/30491493200?pr=19641 already fixed in the latest master |
@4brunu all tests passed. Will merge it tomorrow if no further feedback from anyone. |
I don't know why initially CI was not running on #19621, but now it is running |
I updated the setting in bitrise.io to trigger the workflow when there's a change to the new folders for swift6 samples. here are the folders/paths that will trigger a build when there's change:
|
PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master
(upcoming7.x.0
minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)