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.

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

Fix issue where CustomSeverities are not respected in config #459

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

zph
Copy link
Contributor

@zph zph commented Jun 22, 2024

Original ability was added in: #281

When trying out the functionality, it does not respect custom_severities as documented in the README.

This patch addresses it by including the porting of custom severities from the the same location where other config keys are copied

I've confirmed that it works both in a new test and in manual regression testing.

Fixes: #364

Side note: I didn't include further changes but it looks like golang is auto-formatting code in the project differently than what's committed in the files I touched. It's a good idea to do a single code formatting re-write so you don't have a trickle of whitespace/formatting changes in PRs.

Original ability was added in: thoughtworks#281

When trying out the functionality, it does not respect custom_severities
as documented in the README.

This patch addresses it by including the porting of custom severities
from the the same location where other config keys are copied

I've confirmed that it works both in a new test and in manual regression
testing.

Fixes: thoughtworks#364
@deepthirera deepthirera merged commit 666644d into thoughtworks:main Jun 26, 2024
4 checks passed
@zph zph deleted the zh-fix-missing-custom-severities branch June 27, 2024 15:35
deepthirera pushed a commit to deepthirera/talisman that referenced this pull request Jul 19, 2024
…works#459)

Original ability was added in: thoughtworks#281

When trying out the functionality, it does not respect custom_severities
as documented in the README.

This patch addresses it by including the porting of custom severities
from the the same location where other config keys are copied

I've confirmed that it works both in a new test and in manual regression
testing.

Fixes: thoughtworks#364
deepthirera added a commit to deepthirera/talisman that referenced this pull request Jul 19, 2024
deepthirera added a commit that referenced this pull request Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configuring custom severities not working with pre-push
2 participants