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

Fix Danger CI not running #8299

Merged
merged 1 commit into from
Nov 4, 2024
Merged

Fix Danger CI not running #8299

merged 1 commit into from
Nov 4, 2024

Conversation

FelixMalfait
Copy link
Member

The Danger CI was not running anymore (we need it for CLA/Congrats bot)

@FelixMalfait FelixMalfait merged commit 740ca55 into main Nov 4, 2024
15 checks passed
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

Modified CI Utils workflow to ensure Danger.js and congratulatory messages run on every PR by removing the file-specific check constraints.

  • Removed path filters that previously limited CI to only packages/twenty-utils changes
  • Inconsistent token usage between jobs: github.token for danger-js vs secrets.GITHUB_TOKEN for congratulate
  • Added pull_request_target event trigger with appropriate security considerations
  • Configured concurrency settings to prevent parallel workflow runs

1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

Comment on lines 30 to 31
env:
DANGER_GITHUB_API_TOKEN: ${{ github.token }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

style: Using github.token here but secrets.GITHUB_TOKEN below. Should be consistent between both jobs.

@FelixMalfait FelixMalfait deleted the fix-utils-ci branch November 4, 2024 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant