-
Notifications
You must be signed in to change notification settings - Fork 364
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
Correct spelling mistake #411
Conversation
Tipp -> Tip on line 67
Hi @richardfergie! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Thanks for detecting this typo. Unfortunately, we do not accept such commits as a collaboration. We will definitely fix this typo soon, but no need to push new commits nor pull requests for this simple text change. Thanks though! |
Yeah, no problem. Is there a better way to let you know about these things?
…On Wed, 22 Jun 2022 at 00:07, laresbernardo ***@***.***> wrote:
Thanks for detecting this typo. Unfortunately, we do not accept such
commits as a collaboration. We will definitely fix this typo soon, but no
need to push new commits nor pull requests for this simple text change.
Thanks though!
—
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAS7USN6R5PBEJAJCQCS5RDVQJDKRANCNFSM5ZCVQWBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for understanding. You can always create an issue referring to where the typos are and we will fix them in the following batch of commits. |
Tipp -> Tip on line 67
Project Robyn
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # (issue)
No issue number or anything like that, just correcting a minor spelling mistake in a comment/documentation line