-
Notifications
You must be signed in to change notification settings - Fork 6
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
Am/chore/wasm support #39
Conversation
8d00f63
to
67e2f40
Compare
407a434
to
aacd63a
Compare
b8ec9b8
to
8801de7
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.
From a CI point of view everything is fine to me.
Just letting @tmontaigu for the final approval.
@@ -12,7 +12,7 @@ jobs: | |||
- name: Check first line | |||
uses: gsactions/commit-message-checker@16fa2d5de096ae0d35626443bcd24f1e756cafee | |||
with: | |||
pattern: '^((feat|fix|chore|refactor|style|test|docs|doc)\(\w+\)\:) .+$' | |||
pattern: '^((feat|fix|chore|refactor|style|test|docs|doc)(\([\w\-_]+\))?\!?\:) .+$' |
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.
Can you clarify the case you want to avoid ? If I undertand correctly you allow hypen and underscore within the parenthesis but not the exclamation mark right ?
What was the issue you've encountered ?
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.
it's something we did with Nico on the TFHE-rs repo to allow hypens, make the content of the parentheses optional and the ! is to allow indicating breaking change as conventional commits permits
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.
bangère
Adapatation of #32 by @On0n0k1