Use Main branch in the docs instead of old Master branch #2164
Conversation
While referring to the Contributing.md as a new contributor, I noticed that the guidelines still reference outdated Master branch and its docs. This PR updates Contributor guidelines and other docs to use the latest Main branch of the Tutorial repo instead of the Master branch.
|
Hi @spzala! 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@meta.com. Thanks! |
|
Thanks so much for your contribution! Please sign the CLA and we'll be happy to merge. |
|
Hi @svekars thank you so much for the quick review and comment!!! I am working on it and hoping to have it done quickly. |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
|
@svekars a quick update, CLA is done :) Thank you so much again! |
While referring to the
CONTRIBUTING.mdas a new contributor, I noticed that the guidelines still reference outdatedMasterbranch and its docs. This PR updates Contributing guidelines and other docs to use the latestMainbranch of the Tutorial repo instead of theMasterbranch.