Bruce D'Arcus

Here's [an example](https://gist.github.com/bdarcus/e63cad6748de8af764744272241b6dbb) using `auto-changelog`. Some of the links to issues are broken because I ran on my fork, and it assumes the main repo. Below is the config file,...

In that case, maybe we can maintain a clean, developer-oriented, changelog file here, created with auto-changelog, but manually-edited where we need. You (and whoever else might have time and interest)...

We probably want a [custom template](https://github.com/CookPete/auto-changelog#custom-templates) to organize the output for our needs, and [commit-list helper](https://github.com/CookPete/auto-changelog#commit-list-helper) (see also [this comment](https://github.com/CookPete/auto-changelog/issues/145#issuecomment-576935934)) to define the regex patterns to look for in the...

Proposal, for commit message conventions that will support auto changelog maintanance. ### Summary Format The basic template would be `[type](scope): [Keyword verb] [short detail] [(GH PR number]`. Types: Per [this](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716)...

Good point. As I've been using it in commit messages so far, it is the former. But I'm not wedded to that. I agree, we need to decide.

OK, I updated the draft, but keeping as draft, since I'm still thinking about how best to do this.

Removed the draft on [this post](https://github.com/citation-style-language/schema/issues/220#issuecomment-640047229). I'm not super sure myself, in part because there's duplication. But I'm shooting for conventions that will yield clear [git logs](https://github.com/citation-style-language/schema/commits/master), [milestones](https://github.com/citation-style-language/schema/milestone/3), [changelog](https://github.com/citation-style-language/schema/blob/master/CHANGELOG.md) going...

So also this github action, which would allow us to integrate auto-labeling of issues and PRs based on keywords as well. https://github.com/marketplace/actions/issue-auto-labeling-and-assigning

Exactly. What I'm saying is if we adopt the right conventions for commit log messages, then the auto-updated changelog will actually be useful for those folks, and the auto-label assignment...

The question is, how? Maybe we need a table (say on this project wiki?) with columns for csl, zotero, mendeley, etc. types and variables?