Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ticketAddressResolver not utilized when passed to GitFlow.Configuration #29

Open
novr opened this issue Mar 6, 2024 · 0 comments
Open

ticketAddressResolver not utilized when passed to GitFlow.Configuration #29

novr opened this issue Mar 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@novr
Copy link
Member

novr commented Mar 6, 2024

Bug Description

When passing ticketAddressResolver to GitFlow.Configuration, it seems that the resolver is not being utilized as expected.

Steps to Reproduce

  1. Configure GitFlow.Configuration with ticketAddressResolver.
  2. Execute Danger

Expected Behavior

The ticketAddressResolver should be used according to the configuration when executing Danger.

Actual Behavior

It appears that the ticketAddressResolver is not being utilized, and Danger do not take it into account.
@novr novr added the bug Something isn't working label Mar 6, 2024
@novr novr mentioned this issue Mar 7, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Unused ticketAddressResolver yumemi-inc/danger-swift-eda
1 participant
@novr