react / react/yoga

[Question] Clarification on community pull request acceptance policy

Open
#1,991 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
18.9k
Forks
1.6k
Avg merge
1m
Merged PRs (30d)
1

Description

Hi maintainers 👋,

First of all, thank you for all the work on this project — it’s really impressive and very useful.

While browsing the repository, I noticed something I wanted to better understand regarding the current contribution workflow.

I see that there are quite a number of open pull requests that appear to be unreviewed or unmerged for a long time. At the same time, there are also some recently merged pull requests. However, it seems that the merged ones are primarily from Meta internal contributors .

This made me unsure about the current contribution policy for external/community contributors.

My questions are:

  • Is the project currently still accepting pull requests from the open-source community?
  • If yes, are there any specific criteria or review process differences for external contributors?
  • Are there plans to review or process the existing backlog of community PRs?

I’m asking mainly to understand how I should contribute effectively going forward, and whether I should continue investing time in existing or new pull requests.

Thanks a lot for your time and clarification 🙏

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the contribution-policy questions in issue #1991 and review any existing repository guidance on community pull requests. Done means a maintainer clarifies whether external contributions are accepted, how they are reviewed, and how the backlog will be handled.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.