Javier Godoy
Javier Godoy
@wesleytodd wrote: > So the only officially "spec'd" types are `feat` and `fix`. All additional ones are `etc`, and up to you. I am a fan of pulling some of...
We had the same discussion in our team (https://github.com/FlowingCode/DevelopmentConventions/issues/11). Since we are already using other types from the Angular convention (`build:`, `ci:`, etc) in addition to `feat:` and `fix:`, we...
@damianopetrungaro Is there anything to be dropped? In strict sense, conventional-commits just specify that "_types other than `fix:` and `feat:` are allowed_". The mention of `chore:` is just by means...
Hello. Given the error messages, it seems the User-Agent string actually contains the strings `rv:x.x.x` and `firefox/x.x` in which case, even if it were detected as _firefox over windows xp_...
The proposed change adds 3 characters to the commit header (thereby substracting them from the commit subject, if one wants to keep it below 72 characters). Those 3 characters are...
@Jakub-PMX > @javier-godoy How about `refactor`? It is 8 characters, while `feature` is 7. 🤔 `refactor` is not defined in the conventional commits _specification_ (only `fix` and `feat` are).
The syntax given in the summary already makes clear that body is optional, and footers can be added even if body is absent, as in the example that you referred:...
My colleagues use `deprecate:` We don't like using `feat:` because we reserve it for _introducing new_ features, and we don't like `chore:` either, because it doesn't convey a Semantic Versioning...
The proposal of the `+` sign is interesting. We use conventional-commits in order to enforce alignment with SemVer, i.e. that breaking changes target a new major version, and that changes...