-
Notifications
You must be signed in to change notification settings - Fork 13
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
Integrate TLint into CI #76
Conversation
7ac2ce7
to
65c9b9a
Compare
e5ff163
to
b7d48e6
Compare
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.
Mega LGTM in general, maybe a dependency too much in the CI step.
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.
green from my side
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.
Nice!
Could we use external schemas to do the checking/
Wanda already has its own schema in the guides folder.
This way, we don't depend on updating the linter project if we change the checks structure and the schema.
We could add an optional flag for that, and provider the file.
What do you think?
.github/workflows/ci.yaml
Outdated
uses: actions/checkout@v3 | ||
with: | ||
fetch-depth: 0 | ||
|
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.
Remove newline here to be consistent with the rest of the file
@arbulu89 you are actually right, we have to do that using a build script, I tracked that as a ticket this morning 😄 |
Integrating TLint into the CI so no new checks hit
main
if not compliant