Skip to content

Cannot specify danger_id testing locally #1362

Description

@lukeredpath

Report

What did you do?

I'm trying to test changes to my Dangerfile locally - every time I make changes I can never remember how to do this and the documentation for this isn't that great. I just want to run my Dangerfile against my local file system rather than a specific PR - I just want to test my changes work!

bundle exec danger pr https://github.com/danger/danger/pull/662 --danger_id=prebuild

We use two separate Danger IDs to run pre and post-build checks on CI. I'm trying to test the prebuild flow but the Danger ID is not getting set. It defaults to "danger" every time.

What I really want to be able to do:

bundle exec danger local --danger_id=prebuild

This should not require Github authentication or a PR, it should just run against my local filesystem. Otherwise it isn't really "local", is it?

What did you expect to happen?

I'd expect the danger ID to get set to "prebuild".

What happened instead?

The danger ID is "danger".

Your Environment

  • Local environment
  • Danger 8.3.1
  • Ruby 2.7.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions