8000 set up a continuous integration process to maintain the quality of the code · Issue #15 · jargonLint/jargonLint · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

set up a continuous integration process to maintain the quality of the code #15

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.

Sign up for GitHub

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

Jump to bottom
Open
ccoVeille opened this issue Jun 26, 2024 · 7 comments
Open

set up a continuous integration process to maintain the quality of the code #15

ccoVeille opened this issue Jun 26, 2024 · 7 comments

Comments

@ccoVeille
Copy link
Collaborator

No description provided.

@ccoVeille ccoVeille changed the title set up a continious integration process to maintain the quality of the code set up a continuous integration process to maintain the quality of the code Jun 26, 2024
@ccoVeille
Copy link
Collaborator Author
ccoVeille commented Jun 26, 2024 •
edited
Loading

We can reuse what I did for a personal project ccoVeille/golangci-lint-config-examples#7

    add .vale.ini to setup Vale tool

    .gitignore
    exclude imported Vale Packages

    .yamllint.yaml
    YAML validation, excluding imported Vale Packages

    add .editorconfig to define files format

    add .ecrc to validate files format against .editorconfig
    but, excluding imported Vale Packages

    Git hooks via pre-commit including:
        typos
        codespell
        yamllint

    added following items to GitHub Actions:
        yamllint
        vale
        typos
        codespell
        markdownlint-cli2
        editorconfig-checker

@ccoVeille ccoVeille mentioned this issue Jun 26, 2024
Closed
@ccoVeille
Copy link
Collaborator Author

For records d260bbd was merged with #39, and we miss the fact it broke the yaml

@ccoVeille
Copy link
Collaborator Author

@ccoVeille
Copy link
Collaborator Author

@ccoVeille
Copy link
Collaborator Author

I might also take a look at https://github.com/ls-lint/action

@alexvonme
Copy link
Contributor

I think our current preference seems to be:

  • Follow GitHub preferences for landing page type files such as README.md and CODE_OF_CONDUCT.md
  • Use PascalCase in rules
  • Use snake_case in everything else.

@ccoVeille
Copy link
Collaborator Author

Exactly

@ccoVeille ccoVeille mentioned this issue Jul 6, 2024
Merged
ccoVeille added a commit to ccoveille-forks/jargonLint that referenced this issue Jul 6, 2024
@ccoVeille
ci: fix dependency-review.yml against yamllint rules
2105fb0 
Related to jargonLint#15 and jargonLint#43

Fixes jargonLint#44
This was referenced Jul 6, 2024
Merged
Merged
ccoVeille added a commit that referenced this issue Jul 6, 2024
@ccoVeille
ci: fix dependency-review.yml against yamllint rules
cc89203 
Related to #15 and #43

Fixes #44
@ccoVeille ccoVeille mentioned this issue Jul 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ccoVeille @alexvonme
0