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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add @autopp to Ruby technical committee #2103

Merged
merged 1 commit into from Feb 10, 2019

Conversation

Projects
None yet
2 participants
@ackintosh
Copy link
Member

ackintosh commented Feb 10, 2019

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh, ./bin/security/{LANG}-petstore.sh and ./bin/openapi3/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
  • Filed the PR against the correct branch: master, 3.4.x, 4.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Added @autopp to Ruby technical committee. 馃帀

cc @OpenAPITools/generator-core-team

@wing328 wing328 merged commit 773aa26 into OpenAPITools:master Feb 10, 2019

3 of 4 checks passed

ci/circleci Your tests failed on CircleCI
Details
Shippable Run 5774 status is SUCCESS.
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@wing328 wing328 added this to the 4.0.0 milestone Feb 10, 2019

@ackintosh ackintosh deleted the ackintosh:add-autopp-to-ruby-technical-committee branch Feb 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment