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

build: improve DangerJS checks #2331

Closed
wants to merge 4 commits into from
Closed

Conversation

gidjin
Copy link
Contributor

@gidjin gidjin commented Apr 5, 2023

Summary

Improvements to the DangerJS checks

How To Test

Once #2330 is merged you can trigger the build checks workflow to see danger execute on this branch.

@gidjin gidjin changed the title WIP build: improve DangerJS checks Apr 5, 2023
@gidjin gidjin force-pushed the gidjin/fix-dangerjs-checks branch from 042f12f to ad23e9a Compare April 5, 2023 16:30
@github-actions
Copy link
Contributor

github-actions bot commented Apr 5, 2023

Warnings
⚠️

Changes were made to package.json, but not to yarn.lock - Perhaps you need to run yarn install?

Generated by 🚫 dangerJS against 27b089c

@gidjin gidjin force-pushed the gidjin/fix-dangerjs-checks branch from 472c975 to e61bb5b Compare April 5, 2023 18:01
@gidjin gidjin force-pushed the gidjin/fix-dangerjs-checks branch from e61bb5b to 3a3c8f5 Compare April 6, 2023 16:41
@brandonlenz
Copy link
Contributor

@gidjin anything I can verify here? I see danger has been passing on PRs, including this one. Changes look good to me as well.

@brandonlenz
Copy link
Contributor

I'm also noticing that danger currently fails on main because it's looking for things that are only defined in PR context

@brandonlenz
Copy link
Contributor

@all-contributors please add @gidjin for maintenance

@allcontributors
Copy link
Contributor

@brandonlenz

I've put up a pull request to add @gidjin! 🎉

@werdnanoslen
Copy link
Member

@gidjin what's still needed to merge this?

@gidjin
Copy link
Contributor Author

gidjin commented Jan 22, 2024

@gidjin what's still needed to merge this?

I think I was trying to see how / why Danger didn't run for 3rd party PRs. Since then this isn't blocking PRs and has been running on our own PR so I'm going to close it.

@gidjin gidjin closed this Jan 22, 2024
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.

None yet

4 participants