orhun/git-cliff

Allow multiple parsers for skipped/non-skipped commits

Open

#117 opened on Oct 4, 2022

View on GitHub
 (3 comments) (2 reactions) (0 assignees)Rust (308 forks)auto 404
feature/requestgood first issuehelp wanted

Repository metrics

Stars
 (12,040 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe.

From PR #114:

Note that during testing, one caveat was discovered: If a commit is matched by one parser, it can't be matched by any other. That means if a breaking commit was prevented from being skipped, it won't become part of any other group. Maybe it is worth to think about allowing multiple parsers for commits in an hierarchical order?

Describe the solution you'd like Allow commits to be parsed by multiple commit_parsers (if skipped).

Describe alternatives you've considered None.

Additional context I think this issue needs some brainstorming. Let me know if you want to tackle it!

Contributor guide

Research direction
Examine PR #114 to understand the hierarchical parser logic and implement a solution that allows multiple parsers for commits.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60