Skip to content
GitLab

Add sponsor message in F# giraffe generator

Merged William Cheng requested to merge fsharp-sponsor into master

Add sponsor message in F# giraffe generator

[main] INFO  o.o.codegen.TemplateManager - writing file samples/server/petstore/fsharp-giraffe/.openapi-generator/VERSION
[main] INFO  o.o.codegen.TemplateManager - writing file samples/server/petstore/fsharp-giraffe/.openapi-generator/FILES
################################################################################
# Thanks for using OpenAPI Generator.                                          #
# Please consider donation to help us maintain this project 🙏                 #
# https://opencollective.com/openapi_generator/donate                          #
#                                                                              #
# This generator's contributed by Nick Fisher (https://github.com/nmfisher)    #
# Please support his work directly via https://paypal.me/nickfisher1984 🙏     #
################################################################################

cc @nmfisher

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples: 
    ./mvnw clean package 
./bin/generate-samples.sh
./bin/utils/export_docs_generators.sh
    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*. For Windows users, please run the script in Git BASH.
  • File the PR against the correct branch: master, 5.1.x, 6.0.x
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.