-
Notifications
You must be signed in to change notification settings - Fork 547
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
Linter action with LibreCores CI #960
base: master
Are you sure you want to change the base?
Conversation
Links are broken by github autolinking, the second one is accessible via wallento#5 |
This adds a beta Github action that is run on pushes and pull requests. It automatically annotates the sources with linter issues. Nothing extra is needed beyond merging. Signed-off-by: Stefan Wallentowitz <[email protected]>
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.
Uh, turns out I completely forgot about this; sorry @wallento!
To clarify, this is using Verilator as linter and posts comments as code annotations, while #1427 uses Verible lint and posts lint output as comments (which we can then reply to).
Effectively the two PRs do two different things in two different ways. Since it is not really clear a the moment which approach to present linter output to the user is better, I'm happy to give both approaches a try and we can then improve as we move along.
@@ -0,0 +1,25 @@ | |||
on: [push, pull_request] |
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.
Can you add a license header here?
jobs: | ||
lint: | ||
runs-on: ubuntu-latest | ||
name: Linter |
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.
name: Linter | |
name: RTL lint with Verilator |
This adds a beta Github action that is run on pushes and pull
requests. It automatically annotates the sources with linter issues.
Nothing extra is needed beyond merging.
As a demo you can see how new PRs will fail: wallento#4
They will then show the annotation: wallento@bbf8e10
Removing the current waiver looks like this as a test: wallento@966649b
So, you can see that it will also annotate files outside the changeset.
There will be robustness extensions, but I think it is usable and I would love ibex as beta testers. It can be deactivated or removed as easily as it was added :)