neos / neos/BuildEssentials

Extract list of contributors from the changelog

Open
#54 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
PHP
Stars
9
Forks
10
PR merge metrics
No merged PRs in 30d

Description

As suggested by @markusguenther šŸ” on slack:

11:36 I really like that WordPress is highlighting the contributors of the new versions so nice… maybe also a thing for us šŸ™‚
image

We could extend the CreateChangelog command (or create a new one) to extract the list of the contributors and add it to the end of the log. Then the RM can mention those in the release blog post, which would create a bit of an accomplishment and maybe even something to be proud of for the contributors. At least it was for me back when I got my first contribution into a release.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in build-tools.php around line 214 and read the CreateChangelog command and its surrounding build-toolchain entry points. Determine how changelog data is assembled, then define the contributor list output at the end of the generated log; done means a release changelog includes the contributors in a usable form.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
release, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.