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.