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
Feature: Expose --id to rules #1279
Comments
for now i'll use environment variable in my rules: export const DANGER_ID = process.env.DANGER_ID || 'Danger'; but that's just duplicating the same thing, I need to set the env and need to pass |
Ideas, guides? on how to implement this? |
We run two different Dangerfiles in our repo, so we don't need access to the ID within a single Dangerfile. Is that technique worthwhile for you @glensc?
This then lets us easily trigger different danger files from different events or steps in a Github Actions Workflow, and not have them trip over each other. |
Feels like a field which could be available in the main danger export to me |
@orta, so something here:
just add root level |
I think |
I want to get the value of
danger ci --id
to use in rules.The intent is to run danger twice on CI pipeline, first time early to report coding errors, second time late to grab any artifacts from CI jobs and format them as comments.
The property itself is here:
danger-js/source/commands/ci/runner.ts
Line 66 in 0b2c1d3
The text was updated successfully, but these errors were encountered: