conventional-changelog/standard-version

feat: add configuration option for GitLab/BitBucket URLs

Open

#227 创建于 2017年11月29日

在 GitHub 查看
 (2 评论) (13 反应) (0 负责人)JavaScript (7,442 star) (825 fork)batch import
enhancementhelp wanted

描述

I would like to introduce config options to standard-version, in the form of a .svrc and a standard-version stanza in the package.json; This functionality is built into yargs:

https://github.com/yargs/yargs/blob/master/docs/advanced.md#configuration

I think the first feature we should support is adding the ability to use GitLab and BitBucket style URLs (see https://github.com/conventional-changelog/standard-version/issues/204, https://github.com/conventional-changelog/standard-version/pull/174).

@cdupetit could we potentially simplify the process of providing context for gitlab; it feels like --context requires a lot of variables be specified. I'd prefer that we override a few in the package.json.

贡献者指南

技术栈
javascriptnodejs
领域
toolingrelease
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
basic knowledge of standard versionfamiliarity with yargs configuration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Investigate the existing CLI argument parsing in standard version, likely using yargs. Look at the proposed .svrc config file and the 'standard version' stanza in package.json. Refer to linked issues #204 and PR #174 for context on GitLab/BitBucket URL handling. The main task is to extend the configuration to allow overriding URL patterns for different git hosting services, similar to how yargs handles configuration. Examine the package.json and any existing config loading logic to determine where to integrate the new options.