Skip to content

Feat: Allow repo specific dangerfile. #421

Feat: Allow repo specific dangerfile.

Feat: Allow repo specific dangerfile. #421

Triggered via pull request October 8, 2025 16:57
Status Failure
Total duration 22s
Artifacts

danger-workflow-tests.yml

on: pull_request
pr-analysis
19s
pr-analysis
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 3 warnings, and 2 notices
pr-analysis
Process completed with exit code 1.
pr-analysis: CHANGELOG.md#L0
Please consider adding a changelog entry for the next release.
pr-analysis: undefined#L0
::debug:: Workspace directory contents: .craft.yml, .git, .gitattributes, .github, CHANGELOG.md, LICENSE, README.md, danger, sentry-cli, updater
pr-analysis
::debug:: Current directory contents: .craft.yml, .git, .gitattributes, .github, CHANGELOG.md, LICENSE, README.md, danger, sentry-cli, updater
pr-analysis
Running from a forked repo. Danger won't be able to post comments and workflow status on the main repo, printing directly.
pr-analysis: CHANGELOG.md#L0
### Instructions and example for changelog Please add an entry to `CHANGELOG.md` to the "Unreleased" section. Make sure the entry includes this PR's number. Example: ```markdown ## Unreleased ### Features - Allow repo specific dangerfile ([#129](https://github.com/getsentry/github-workflows/pull/129)) ``` If none of the above apply, you can opt out of this check by adding `#skip-changelog` to the PR description or adding a `skip-changelog` label.
pr-analysis
Do not forget to update <a href="https://github.com/getsentry/sentry-docs">Sentry-docs</a> with your feature once the pull request gets approved.