-
Notifications
You must be signed in to change notification settings - Fork 127
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
Introduce CI and basic checks #99
Conversation
57062f9
to
37db7e8
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.
Nothing to add. Seems good to me. Just don't forget to correct the gitlint error.
Please review the commit phrasing: introduce ci subomodule to submodule
Signed-off-by: Jose Martins <[email protected]>
When including ci.mk in the Makefile it is needed to check if the target rules are rules that will trigger a build or not as most CI rules don't require a build. Otherwise many operations needded only for a build will be triggered even if we are only, for example, checking code formatting. Signed-off-by: Jose Martins <[email protected]>
Signed-off-by: Jose Martins <[email protected]>
Signed-off-by: Jose Martins <[email protected]>
Signed-off-by: Jose Martins <[email protected]>
Done.
Typo fixed. |
Signed-off-by: Jose Martins <[email protected]>
Signed-off-by: Jose Martins <[email protected]>
Just realized the name of the riscv build job was incorrect. Force pushed the correction. |
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.
All good to me.
This PR introduces the bao-ci infrastructure as a git submodule and instantiates and creates Github actions for basic checks such as:
It adds status stickers to the readme file that display the status of the build checks. You can check out how this looks here.