Skip to content

GitHub Workflow #251

@ReidP-source

Description

@ReidP-source

Chet has requested we setup an actions workflow similar to what ear2earth has...

Embedded C++ has some additional steps that will need to be considered before implementing a full workflow. We should start small with a Linter and Formatting then work towards adding tests.

Formatting:
clang-format

https://en.wikipedia.org/wiki/Programming_style

  • Essential for maintaining a consistent format across many modules.

Linter:
clang-tidy

https://en.wikipedia.org/wiki/Lint_%28software%29

  • Identifies possible bugs, suspicious constructs, errors, and style issues automatically.

Tutorial for VScode:
https://www.davidampurua.com/posts/how-to-implement-linter-c/

Tutorial for GitHub Actions:
https://github.com/cpp-linter/cpp-linter-action

Chimes Web workflow example:
https://github.com/OPEnSLab-OSU/WeatherChimesWeb/blob/main/.github/workflows/ci.yml

Linting PP with CCstudio by Texas Instruments:
https://www.ti.com/lit/ml/sprp582/sprp582.pdf?ts=1767649662085&ref_url=https%253A%252F%252Fwww.google.com%252F

  • Code Composer has built-in git integration but it's a whole new IDE.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions