vercel/release

Support for feature branches

Open

#29 opened on Jan 5, 2017

View on GitHub
 (4 comments) (7 reactions) (0 assignees)JavaScript (3,534 stars) (145 forks)batch import
enhancementhelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
clirelease
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Node.js and CLI development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.