Frequently asked questions about contributing to Apache Beam.
About contributing
What should I do after the committer reviews my PR?
The reviewer should give the Looks Good to Me (LGMT) in the PR and then you (the author of the pull request) should rebase, squash, or split, the commits so that the history is useful.
How do I get started contributing to Apache Beam?
See https://beam.apache.org/contribute/
Whom should do I ask if I am stuck?
Either email dev@beam.apache.org or chat on Slack.
How can I opt-in to reviewing pull requests?
- Go to https://github.com/apache/ repo.
- Find the deepest sub-directory that contains the files you want to be a reviewer for.
- Go to the OWNERS file.
- Add your Github username to the file.
- Create a new OWNERS file if necessary.
The Beam project currently uses the reviewers
key in the OWNERS file and no other features, as reviewer selection is still manual.
About Issues
Why can't I assign an issue to myself?
Only Beam committers can self assign directly through the UI. If you are a noncommitter, you can comment .take-issue on the issue and you will be automatically assigned.
I'm a committer - why can't I assign another user?
Non-committers can't be assigned an issue unless they are participating in the thread. The best way to get a non-committer assigned an issue is to tag them on an issue and ask them to comment `.take-issue`. If you surround the command with ` markdown characters it will be ignored so that you don't get assigned yourself.
How do I link a Pull Request to an Issue?
You can link a Pull Request to an Issue by adding #<issue number> in a comment on the PR or in its description. See https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.
About Gradle
OutOfMemoryException during the Gradle build?
See Gradle Tips#OutOfMemoryExceptionduringtheGradlebuild.
About this wiki
Why can't I edit this wiki?
Create a wiki account and then email dev@beam.apache.org to ask for edit access, referencing your account user ID.