esigler / lita-locker

96%

master: 96%

LAST BUILD ON BRANCH DEV-407

branch: DEV-407

CHANGE BRANCH

x

Reset

• DEV-407
• 41
• 42
• DEV-355
• add-events-support
• add-lock-list
• add-queue
• add-status-event
• add_guard_to_give
• add_list
• add_logging
• add_super_basic_rate_limits
• add_timestamp
• avoid-rate-limiting
• comment-regex
• explicit_mentions
• master
• prevent_dequeue
• release_party
• v0.5.0
• v0.5.1
• v0.5.2
• v0.5.3
• v0.7.0
• v1.0.0
• v1.0.1
• v1.0.10
• v1.0.2
• v1.0.3
• v1.0.4
• v1.0.5
• v1.0.6
• v1.0.7
• v1.0.8
• v1.0.9
• v1.1.0
• v1.2.0
• wildcard

Build # 144

Build Type

push

travis-ci

Committed by tristaneuan

Commit Message

Fix unintended behavior with locker status

Currently, sending `locker status foo` will return foo1, foo2, foo3,
etc. if foo does not exist. This is unintended behavior, as all matching
labels should only be returned in response to an explicit wildcard
search. This change makes the bot respond correctly saying that foo does
not exist, with an additional hint that the user should use * for
wildcard search.

(PD internal JIRA issue DEV-407)

Run Details

543 of 564 relevant lines covered (96.28%)

33.99 hits per line