From 108fb7d409f4d8fa35b0651f071a15a9b2cd065a Mon Sep 17 00:00:00 2001 From: Rodrigo de Salvo Braz Date: Mon, 12 Feb 2024 15:44:46 -0800 Subject: [PATCH] Update CONTRIBUTING.md Summary: Including explanation of how PRs are merged into a Meta open source project in the Pull Requests section of the `CONTRIBUTING.md` page. Reviewed By: xuruiyang Differential Revision: D53686017 fbshipit-source-id: 4db474f54aeeba206d97a4a1eaaaa8bd8caa92d3 --- CONTRIBUTING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 31a46710..a1181891 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -11,6 +11,8 @@ issue before starting any pull requests. ## Pull Requests We actively welcome your pull requests. +Note: pull requests are not imported into the GitHub directory in the usual way. There is an internal Meta repository that is the "source of truth" for the project. The GitHub repository is generated *from* the internal Meta repository. So we don't merge GitHub PRs directly to the GitHub repository -- they must first be imported into internal Meta repository. When Meta employees look at the GitHub PR, there is a special button visible only to them that executes that import. The changes are then automatically reflected from internal Meta repository back to GitHub. This is why you won't see your PR having being directly merged, but you still see your changes in the repository once it reflects the imported changes. + 1. Fork the repo and create your branch from `main`. 2. If you've added code that should be tested, add tests. 3. If you've changed APIs, update the documentation.