mergiraf/mergiraf
mergiraf/mergiraf
9
213
Fork 45
Code Issues 50 Pull requests 6 Releases 19 Activity Actions

chore: Highlight new contributors in release notes #528

Merged
wetneb merged 2 commits from wetneb/highlight_new_contributors into main 2025-07-23 21:53:25 +02:00 AGit
Conversation 1 Commits 2 Files changed 1 +13 -1
wetneb commented 2025-07-23 20:17:20 +02:00
Owner
Copy link

It adds something like this to the release notes (for 0.13.0 as an example):

## 🎉 New contributors

- @twz123 made their first contribution in #510 
- @jadeprime made their first contribution in #508
It adds something like this to the release notes (for 0.13.0 as an example): ``` ## 🎉 New contributors - @twz123 made their first contribution in #510 - @jadeprime made their first contribution in #508 ```
chore: Highlight new contributors in release notes
All checks were successful
/ test (pull_request) Successful in 38s
Details
5adef49b4a
ada4a approved these changes 2025-07-23 20:25:12 +02:00
ada4a left a comment
Owner
Copy link

Good idea!

Good idea!
cliff.toml
@ -22,0 +24,4 @@
{% if gitea.contributors | filter(attribute="is_first_time", value=true) | length != 0 %}
## 🎉 New contributors
{% endif %}\
{% for contributor in gitea.contributors | filter(attribute="is_first_time", value=true) %}
ada4a commented 2025-07-23 20:25:03 +02:00
Owner
Copy link

The diff does looks sensible, but I wish there was a way to do a test release and see how it actually renders out. I guess we could actually create some sort of a UI test by running git-cliff on a pre-defined revision range, and checking if its new output (after a given PR) still makes sense

The diff does looks sensible, but I wish there was a way to do a test release and see how it actually renders out. I guess we could actually create some sort of a UI test by running git-cliff on a pre-defined revision range, and checking if its new output (after a given PR) still makes sense
wetneb commented 2025-07-23 20:26:14 +02:00
Author
Owner
Copy link

You can just run git-cliff --latest locally from the PR branch to see the result. It's what the CI runs for the release.

You can just run `git-cliff --latest` locally from the PR branch to see the result. It's what the CI runs for the release.
wetneb commented 2025-07-23 20:28:41 +02:00
Author
Owner
Copy link

Hmm I realize the heading is a bit too big (see the updated release notes for 0.13.0), I'll rather bring it to the same level as the commit categories.

Hmm I realize the heading is a bit too big (see [the updated release notes for 0.13.0](https://codeberg.org/mergiraf/mergiraf/releases/tag/v0.13.0)), I'll rather bring it to the same level as the commit categories.
ada4a commented 2025-07-23 21:16:00 +02:00
Owner
Copy link

You can just run git-cliff --latest locally from the PR branch to see the result. It's what the CI runs for the release.

Thanks for the tip! That's good to know

> You can just run `git-cliff --latest` locally from the PR branch to see the result. It's what the CI runs for the release. Thanks for the tip! That's good to know
Make heading smaller
All checks were successful
/ test (pull_request) Successful in 38s
Details
5f4df4fd9f
wetneb merged commit 219ac7e4b3 into main 2025-07-23 21:53:25 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
ada4a
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind
Bad merge
Examples where the merging algorithm doesn't work as well as it should

  
Kind
Bug
Something is not working

  
Kind
Documentation
Documentation changes

  
Kind
Enhancement
Improve existing functionality

  
Kind
Feature
New functionality

  
Kind
New language

  
Kind
Security
This is security issue

  
Kind
Testing
Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Compat/Breaking
Kind
Bad merge
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
New language
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: mergiraf/mergiraf#528
No description provided.
Delete branch "wetneb/highlight_new_contributors"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?