vercel/release

Support for feature branches

Open

#29 建立於 2017年1月5日

在 GitHub 查看
 (4 留言) (7 反應) (0 負責人)JavaScript (3,534 star) (145 fork)batch import
enhancementhelp wanted

描述

My team uses feature branches, and we also use the "Squash and merge" feature within GitHub. This makes our master branch look like this (by default):

image

So, do you think it would be possible for release to detect commit messages in that format (instead of using parenthesis such as Error logging works now (patch))? The Angular guidelines could be used:

listed under ### Minor Changes:

  • feat
  • feature

listed under ### Patches:

  • fix
  • docs
  • style
  • refactor
  • perf
  • test
  • chore

So anything that begins with those words would automatically be sorted to minor or patch.

貢獻者指南

技術棧
javascriptnodejs
領域
clirelease
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with Node.js and CLI development
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Investigate how the current release tool parses commit messages (likely in the main source code). Look for existing parsing logic that detects parenthetical markers like (patch) and modify to also support prefix based markers like 'feat:' and 'fix:' based on the Angular commit guidelines. Check the repository's CONTRIBUTING.md for contribution guidelines and existing tests. Consider compatibility with existing configurations.