Skip to content

README badges #45

Open
Open
@mgcooper

Description

@mgcooper

I tried to fork and pull request these changes but as far as I can tell I cannot confirm if the fixes work unless they're done on the main branch (I think the matlab checkout feature only runs on the default branch). So I figured I'd just summarize them here.

In README:

  • The miss_hit badge should be deleted right? since pre commit is doing it?
  • The matlab test and coverage badge needs the extension to change from .yaml to .yml i.e. .github/workflows/matlab_test_and_coverage.yaml should be .github/workflows/matlab_test_and_coverage.yml

In matlab_test_and_coverage.yml:

  • It might be necessary to make the matlab version consistent in the setup and run steps:
    • uses: matlab-actions/[email protected]
    • uses: matlab-actions/[email protected]
    • (Not sure that's necessary, I thought it was why the tests failed on my fork but more likely due to other reasons)

Other changes:

  • I had to add .vscode/settings.json file to override my autoIndent settings otherwise the yml files were being indented with two spaces instead of four.
"[yml]": {
        "editor.tabSize": 4,
        "editor.insertSpaces": true,
        "editor.detectIndentation": false
    }
  • I also had to add a .prettierrc file to the top-level to override the yml indenting. Lots of people use prettier so this may be worth adding to the repo. This is the entire contents of the file:
{
  "tabWidth": 4,
  "useTabs": false
}

Unlike the matlab version thing, the indenting actually did cause the tests to fail, since the pre-commit settings enforce 4 spaces.

Feel free to take or leave any of these suggestions. I would have issued a PR but I spent a stupid amount of time trying to get the CI tests to run on a temporary fix branch of my fork and couldn't get them to go, so I gave up. Thanks for the nice template.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions