Problem/Motivation

We want to be able to automate as much as possible for release management.

Proposed resolution

Set up semantic-release to automatically bump versions and create changelogs. Using this tools means making use of a more conventional commit format such as: https://www.conventionalcommits.org/en/v1.0.0/ and enforcing this standard with a tool such as commitizen

The only addition to this would be to define a "Credit" or "By" footer listing all users to be credited for a particular issue/commit..

An example of a commit (taken from once history):

fix(once): Error when context.querySelector() doesn't find an element on the page

Credits: nod_, Danny Englander, droplet
Refs #3204168

Here the (once) is optional, in the mono repo we might want to explicitly tell which package we're handling (semantic release tools don't need it to know which package is impacted by the commit, so totally optional, only for humans).

Comments

nod_ created an issue. See original summary.

nod_’s picture

Parent issue: » #3220681: Setup monorepo
larowlan’s picture

I'm in favour of this, using it for a few npm packages I maintain, it is effortless

podarok’s picture

Project: Drupal core JavaScript packages » Drupal.org customizations
Version: » 7.x-3.x-dev
Component: Other » Code
Issue tags: +UX

I guess this is not related to just the current project, but for the whole drupal.org infrastructure
Would be great to have e.g. https://www.drupal.org/node/2846603/commits somehow parsed and visually improved
As well as release creation process to get changelog generation based on this list

nod_’s picture

Project: Drupal.org customizations » Drupal core JavaScript packages
Version: 7.x-3.x-dev »
Component: Code » Once

This is specifically a policy for this general project used for some of the core JS. This is to agree on a new core policy for commit format, not d.o integration.

Please open a new on for general availability/support/integration for other projects on d.o.

nod_’s picture

Title: Use conventional commit format » [policy] Use conventional commit format
nod_’s picture

Component: Once » Other
Issue tags: -UX
e0ipso’s picture

I have been using semantic release and commitlint successfully for a while now, and I have only good words for it. Big plus one from me.

bbrala’s picture

quietone’s picture

Status: Active » Closed (duplicate)
Related issues: +#3439331: [policy] Decide on format of commit message

Yes, I agree with #9. This should have been cleanup when that work was finished.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.