beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] incubator-beam pull request #1083: [BEAM-742] Replicate triggers to runners-...
Date Wed, 12 Oct 2016 04:54:09 GMT
GitHub user kennknowles opened a pull request:

    [BEAM-742] Replicate triggers to runners-core (migration step towards conversion to AST)

    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.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

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

    $ git pull TriggerReactor

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 #1083
commit 241566d0e47d972b5afa7a0ab43b856dddb60ed6
Author: Kenneth Knowles <>
Date:   2016-06-24T03:05:27Z

    Move triggers to runners-core
    This commit is effectively a "git hint" that all the files
    in runners-core are moved from prior files. The moved files
    will be replaced.

commit 4465a589af483db3bbf0ec1c90517fc57a67631a
Author: Kenneth Knowles <>
Date:   2016-06-24T03:31:10Z

    Rename trigger reactors

commit 3a79b875bb28f659e90e9aae8e844022ea3546dd
Author: Kenneth Knowles <>
Date:   2016-10-12T04:35:02Z

    Restore prior trigger files, for temporary compatibility


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