beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mbuccini <>
Subject [GitHub] incubator-beam pull request #1245: [Beam-693] Update Readme with instruction...
Date Tue, 01 Nov 2016 11:03:29 GMT
GitHub user mbuccini opened a pull request:

    [Beam-693] Update Readme with instructions about pydoc requirement

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [X] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [X] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    this PR includes an update for the README file so that users will be able to fix import
errors when using pydoc without having all required packages installed.
    I didn't check for TravisCI/mvn clean verify because only the README file has changed.

You can merge this pull request into a Git repository by running:

    $ git pull beam-693

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1245
commit 16209bf8972f5d3a3deb26b7586a4d66d545f4c5
Author: Marco Buccini <>
Date:   2016-11-01T09:17:25Z

    updated readme according to BEAM-693

commit a213841bbb61feb69cc6d419782ff221e59a0948
Author: Marco Buccini <>
Date:   2016-11-01T09:19:00Z

    Removed newline


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message