Skip to content

Map new message identifiers to all existing entries (from the Tags repository & the client message cache storage) of the same message when it is moved #85

Map new message identifiers to all existing entries (from the Tags repository & the client message cache storage) of the same message when it is moved

Map new message identifiers to all existing entries (from the Tags repository & the client message cache storage) of the same message when it is moved #85

Triggered via pull request November 27, 2024 16:41
@mercihabammercihabam
edited #1388
Status Failure
Total duration 11s
Artifacts

test.lint.pr.yml

on: pull_request_target
Validate PR title
2s
Validate PR title
Fit to window
Zoom out
Zoom in

Annotations

1 error
Validate PR title
No release type found in pull request title "Map new message identifiers to all existing entries (from the Tags repository & the client message cache storage) of the same message when it is moved". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit