-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add GitHub annotations for lint #625
Conversation
🦋 Changeset detectedLatest commit: 21dfb66 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll take a closer look next week but this looks seriously impressive! Thanks a bunch 🤩
src/cli/lint/external.ts
Outdated
const tools = [ | ||
...(eslint.ok ? [] : ['ESLint']), | ||
...(prettier.ok ? [] : ['Prettier']), | ||
...(tscOk ? [] : ['tsc']), | ||
]; | ||
|
||
const summary = `${tools.join(', ')} found issues that require triage.`; | ||
await createAnnotations(eslint, prettier, tscOk, tscOutputStream, summary); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for a separate PR, but any thoughts on error handling for annotations? I'm thinking that we should log and continue, rather than failing the command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I was thinking it should log a warning/error - we shouldn't fail the whole test if we simply fail to report
Moves the Buildkite annotation refactoring logic out of #625. This will enable us to add different types of annotations and aid in writing unit tests without cluttering the external file. Co-authored-by: Ryan Ling <[email protected]>
Co-authored-by: Ryan Ling <[email protected]>
Co-authored-by: Ryan Ling <[email protected]>
Co-authored-by: Ryan Ling <[email protected]>
Co-authored-by: Ryan Ling <[email protected]>
Co-authored-by: Ryan Ling <[email protected]>
Co-authored-by: Ryan Ling <[email protected]>
…nto github-lint-annotations
Co-authored-by: Ryan Ling <[email protected]>
…nto github-lint-annotations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you!
Features:
Changes:
Screenshots
Status View
Check Run Page View
Files Changed View