Skip to content

ci: prevent badly formed commit messages #94

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
Merged
merged 2 commits into from
Feb 8, 2025
Merged

ci: prevent badly formed commit messages #94

merged 2 commits into from
Feb 8, 2025

Conversation

MatheusBaldi
Copy link
Contributor

npm run commitlint was missing in the npm run standards script.

@coveralls
Copy link

coveralls commented Feb 7, 2025 •
edited
Loading

Coverage Status

coverage: 98.663%. remained the same
when pulling 6b15b11 on MatheusBaldi:MatheusBaldi/prevent-badly-formed-commit-messages
into cc79c46 on silvermine:master.

@MatheusBaldi MatheusBaldi force-pushed the MatheusBaldi/prevent-badly-formed-commit-messages branch from 077ce0a to 6b15b11 Compare February 7, 2025 21:53
onebytegone
onebytegone approved these changes Feb 8, 2025
View reviewed changes
Copy link
Contributor

@onebytegone onebytegone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @MatheusBaldi!

@onebytegone onebytegone merged commit a7b6c54 into silvermine:master Feb 8, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@onebytegone onebytegone onebytegone approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@MatheusBaldi @coveralls @onebytegone