Skip to content

ci: fix changelog creation and update contribution guide - #80

Open
lheppler wants to merge 4 commits into
eclipse-esmf:mainfrom
bci-oss:fix-changelog-creation
Open

ci: fix changelog creation and update contribution guide#80
lheppler wants to merge 4 commits into
eclipse-esmf:mainfrom
bci-oss:fix-changelog-creation

Conversation

@lheppler

@lheppler lheppler commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Description

fix changelog creation and update contribution guide for conventional commits

Fixes #79

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have made corresponding changes to the documentation

@Hanna-Shalamitskaya-EPAM Hanna-Shalamitskaya-EPAM left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good for me

lheppler added 3 commits July 30, 2026 12:29
The previously documented Conventional Commits convention prescribes a
fixed set of types that say little about this repository, and it ties
the commit log to changelog generation.

Describe the Scoped Commits convention (https://scopedcommits.com/)
instead: the subject names the subsystem a commit touches, and the
changelog is written for users rather than derived from the git log.
The changelog step used requarks/changelog-action, which parses
Conventional Commits. Under the scoped commits convention every commit
is an "invalid commit" to it, so excludeTypes filtered nothing and the
output degenerated into a flat list of subjects.

Let GitHub generate the change list from the merged pull requests of the
release instead, keeping the changelog independent of the git log. Also
replace the remaining conventional-commit vocabulary in the version bump
job.
The release workflow wrote "Release version X" and "Bump development
version to X", which carry no scope. They are ordinary commits rather
than the reverts and merges that CONTRIBUTING.md exempts, so they should
follow the same convention contributors do.

Tag annotations and the GitHub release title are left untouched - they
are user-facing labels, not commit messages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Task] Include all major changes in the release notes

2 participants