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

chore: fix linters failing due to relative typescript include paths #110

Merged
merged 1 commit into from
Apr 15, 2024

Conversation

FreekVR
Copy link
Contributor

@FreekVR FreekVR commented Apr 15, 2024

No description provided.

@FreekVR FreekVR requested review from a team as code owners April 15, 2024 10:40
Copy link

netlify bot commented Apr 15, 2024

Deploy Preview for myparcel-developer-portal ready!

Name Link
🔨 Latest commit 6c3ae40
🔍 Latest deploy log https://app.netlify.com/sites/myparcel-developer-portal/deploys/661d04358be9640008f28b86
😎 Deploy Preview https://deploy-preview-110--myparcel-developer-portal.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@EdieLemoine EdieLemoine added this pull request to the merge queue Apr 15, 2024
@myparcel-bot myparcel-bot bot added the approved (Auto) label Apr 15, 2024
Merged via the queue into main with commit a502fd5 Apr 15, 2024
11 checks passed
@EdieLemoine EdieLemoine deleted the feat/fix-typescript-eslint-paths branch April 15, 2024 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved (Auto)
Development

Successfully merging this pull request may close these issues.

3 participants