Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge are not done automatically, message received is "Doing nothing since push event affects no open pull requests" #175

Open
fintecheando opened this issue Mar 30, 2020 · 1 comment
Labels
question Questions about how to use or configure Bulldozer

Comments

@fintecheando
Copy link

fintecheando commented Mar 30, 2020

Hi,

I got the .bulldozer.yml defined with these settings:

# "version" is the configuration version, currently "1".
version: 1

# "merge" defines how and when pull requests are merged. If the section is
# missing, bulldozer will consider all pull requests and use default settings.
merge:
  # "whitelist" defines the set of pull requests considered by bulldozer. If
  # the section is missing, bulldozer considers all pull requests not excluded
  # by the blacklist.
  whitelist:
    # Pull requests with any of these labels (case-insensitive) are added to
    # the whitelist.
    labels: ["merge when ready"]

    # Pull requests where the body or any comment contains any of these
    # substrings are added to the whitelist.
    comment_substrings: ["==MERGE_WHEN_READY=="]

    # Pull requests where any comment matches one of these exact strings are
    # added to the whitelist.
    comments: ["Please merge this pull request!"]

    # Pull requests where the body contains any of these substrings are added
    # to the whitelist.
    pr_body_substrings: ["==MERGE_WHEN_READY=="]

    # Pull requests targeting any of these branches are added to the whitelist.
    branches: ["develop"]

  # "blacklist" defines the set of pull request ignored by bulldozer. If the
  # section is missing, bulldozer considers all pull requests. It takes the
  # same keys as the "whitelist" section.
  blacklist:
    labels: ["do not merge"]
    comment_substrings: ["==DO_NOT_MERGE=="]

  # "method" defines the merge method. The available options are "merge",
  # "rebase", and "squash".
  method: squash

  # Allows the merge method that is used when auto-merging a PR to be different based on the
  # target branch. The keys of the hash are the target branch name, and the values are the merge method that
  # will be used for PRs targeting that branch. The valid values are the same as for the "method" key.
  # Note: If the target branch does not match any of the specified keys, the "method" key is used instead.
  branch_method:
    develop: squash
    master: merge

  # "options" defines additional options for the individual merge methods.
  options:
    # "squash" options are only used when the merge method is "squash"
    squash:
      # "title" defines how the title of the commit message is created when
      # generating a squash commit. The options are "pull_request_title",
      # "first_commit_title", and "github_default_title". The default is
      # "pull_request_title".
      title: "pull_request_title"

      # "body" defines how the body of the commit message is created when
      # generating a squash commit. The options are "pull_request_body",
      # "summarize_commits", and "empty_body". The default is "empty_body".
      body: "empty_body"

      # If "body" is "pull_request_body", then the commit message will be the
      # part of the pull request body surrounded by "message_delimiter"
      # strings. This is disabled (empty string) by default.
      message_delimiter: ==COMMIT_MSG==

  # "required_statuses" is a list of additional status contexts that must pass
  # before bulldozer can merge a pull request. This is useful if you want to
  # require extra testing for automated merges, but not for manual merges.
  required_statuses:
    - "ci/circleci: ete-tests"

  # If true, bulldozer will delete branches after their pull requests merge.
  delete_after_merge: true

# "update" defines how and when to update pull request branches. Unlike with
# merges, if this section is missing, bulldozer will not update any pull requests.
update:
  # "whitelist" defines the set of pull requests that should be updated by
  # bulldozer. It accepts the same keys as the whitelist in the "merge" block.
  whitelist:
    labels: ["WIP", "Update Me"]

  # "blacklist" defines the set of pull requests that should not be updated by
  # bulldozer. It accepts the same keys as the blacklist in the "merge" block.
  blacklist:
    labels: ["Do Not Update"]

Nothing is merged, and I got the following messages:

bulldozer_1  | {"level":"debug","rid":"bq14ogmu2rnkeou5j130","github_event_type":"push","github_delivery_id":"f44f3fdc-72be-11ea-9665-f31fb3d2217a","github_installation_id":7656454,"github_repository_owner":"InfotecMexico","github_repository_name":"bulldozer","time":"2020-03-30T19:45:06.194790641Z","message":"received push event with base ref refs/heads/develop"}
bulldozer_1  | {"level":"debug","rid":"bq14ogmu2rnkeou5j130","github_event_type":"push","github_delivery_id":"f44f3fdc-72be-11ea-9665-f31fb3d2217a","github_installation_id":7656454,"github_repository_owner":"InfotecMexico","github_repository_name":"bulldozer","time":"2020-03-30T19:45:06.194809291Z","message":"Doing nothing since push event affects no open pull requests"}
bulldozer_1  | {"level":"info","rid":"bq14ogmu2rnkeou5j130","method":"POST","path":"/api/github/hook","status":200,"size":0,"elapsed":86.030881,"time":"2020-03-30T19:45:06.194823982Z","message":"http_request"}

Is there any setting that should be changed?

Regards

@asvoboda
Copy link
Member

That log message is from the push event handler, which is used for updating other branches. See the config under update.

You'll want to try the following to auto-merge PRs (with your config):

  1. Open a new PR on against your default branch
  2. Make sure bulldozer is either on the list of allowed merges
  3. Apply the label merge when ready, and create it if necessary
  4. Wait until all required status checks are green
  5. PR should be automatically merged

Check the readme for other common troubleshooting problems.

@asvoboda asvoboda added the question Questions about how to use or configure Bulldozer label Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions about how to use or configure Bulldozer
Projects
None yet
Development

No branches or pull requests

2 participants