vercel/release

Support for feature branches

Open

Aperta il 5 gen 2017

Vedi su GitHub
 (4 commenti) (7 reazioni) (0 assegnatari)JavaScript (3534 star) (145 fork)batch import
enhancementhelp wanted

Descrizione

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.

Guida contributor

Tech stack
javascriptnodejs
Dominio
clirelease
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Familiarity with Node.js and CLI development
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
50
Direzione di ricerca
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.