mathieudutour/github-tag-action

Support gitmoji commits

Open

#67 opened on Mar 12, 2021

View on GitHub
 (2 comments) (1 reaction) (0 assignees)TypeScript (222 forks)github user discovery
good first issue

Repository metrics

Stars
 (720 stars)
PR merge metrics
 (PR metrics pending)

Description

Thanks for creating this great action! I would like to use is with gitmoji based commits like 📝(README): Updated README with info, but it seems not possible with the current separators. As the above example, which refers to the docs: conventional commits type, can also be represented by :memo:(README): Updated README with info, I thought I can just add them to the custom_release_rules. Unfortunately, as the separator : is hardcoded here https://github.com/mathieudutour/github-tag-action/blob/87322e4efff34a7f630512379aabad45e3254d53/src/utils.ts#L76 it's not possible to add them like :zap::patch, :bug::patch, :ambulance::patch, :sparkles::minor etc.. My suggestion would be to either have optional separators with two new parameters (:zap:,patch; :bug:,patch; ...) or to use another data representation of the custom_release_rules. What do you think @mathieudutour ?

Contributor guide

Research direction
Implement support for custom separators in the commit parsing logic, allowing emoji prefixes like ':zap:' with optional separators (e.g., comma). Modify the custom release rules to accept alternative separators or use a different data structure.
Tech stack
typescriptgithub actions
Domain
devopsci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Mostly clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70