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

πŸ’š (ci) [NO-ISSUE]: Allow some ref to skip dangercheck #64

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

valpinkman
Copy link
Member

πŸ“ Description

Allow dependabot to run the CI even without DangerJS formatting

❓ Context

  • JIRA or GitHub link:

βœ… Checklist

Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

  • Covered by automatic tests.
  • Impact of the changes:
    • ...

🧐 Checklist for the PR Reviewers

  • The code aligns with the requirements described in the linked JIRA or GitHub issue.
  • The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
  • There are no undocumented trade-offs, technical debt, or maintainability issues.
  • The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
  • Any new dependencies have been justified and documented.

Copy link

vercel bot commented Apr 17, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
device-sdk-ts-sample βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Apr 17, 2024 4:20pm

@valpinkman valpinkman changed the title πŸ’š (ci): [NO-ISSUE]: Allow some ref to skip dangercheck πŸ’š (ci) [NO-ISSUE]: Allow some ref to skip dangercheck Apr 17, 2024
@valpinkman valpinkman merged commit 641f0ac into develop Apr 23, 2024
13 of 14 checks passed
@valpinkman valpinkman deleted the chore/no-issue-dependabot branch April 23, 2024 08:00
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.

3 participants