semantic-release / semantic-release/commit-analyzer

Feature request

Open
#602 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
448
Forks
82
Avg merge
17h 41m
Merged PRs (30d)
4

Description

I'd like the option to be able to ignore strings that match a pattern that nog prevent the commit analyzer from working with DevOps commits.

As is wel documented in this issue (https://developercommunity.microsoft.com/t/Change-default-title-for-pull-request-co/365716), DevOps insists on prefixing a pull request with the text Merged PR ####. This means that the title feat: Updated Program.cs becomes Merged PR 8324: feat: Updated Program.cs af the merge.

If it would be possible te specify een regular expression to ignore these words the problem would be solved. Of course it would be nice to also have the text feat: Updated Program.cs in the release note instead of Merged PR 8324: feat: Updated Program.cs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named in the issue; start by locating the commit-title parsing and configuration entry points. Add a configurable regular expression for stripping prefixes such as “Merged PR ####:” and verify that the remaining conventional title is analyzed and appears in the release note.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
release
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.