committed
committed copied to clipboard
crate-ci
Nitpicking commit history since beabf39
A problem I've seen with contributors is picking meaningful scopes. If committed could help show people what scopes are commonly used, it'd be a big help.
This is at least for the conventional parsing. See https://github.com/crate-ci/typos/pull/387#issuecomment-994092352 for the idea. When we define a context, I think it saves off the input string, so we can look...
As suggested in https://github.com/crate-ci/typos/pull/387 Options I found - https://github.com/marketplace/actions/welcome-new-contributors - https://github.com/marketplace/actions/welcome-new-users - https://github.com/rust-lang/highfive High Five is the nicest with path-based messages,expected branch handling, etc. The problem is its a bit...
Building blocks - A flag to report breaking changes - Conditionals - https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif - https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions - A means of applying labels - like https://selleo.com/til/posts/iumvmfrkhn-automate-pull-request-labels-via-github-actions
I don't think github has published their regex for finding `Closes #...` but gitlab has. We can take that and run it against the subject and description. If results show...
Use cases - A workspace might have multiple changelogs - We don't know how to map a commit to a changelog - Users might extend the list of changelogs -...
Seems like some people might like this as an optional feature See https://github.com/LDNOOBW/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words