Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Config shouldn't be case sensitive
See original GitHub issueMy yaml file contains the following:
issue-labels-include:
- Breaking change
- Bug
- New Feature
but my GitHub labels are lower case. For instance: “new feature”, “bug”, etc.
As a result of this case sensitivity issue, GitReleaseManager will generate release notes like this instead of the expected notes that should look like this.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Case-insensitive sections in ConfigParser - python
By default, section names are case sensitive but keys are not [1]. For the footnote it says. [1] (1, 2, 3, 4, 5,...
Read more >Config should NOT be case sensitive · Issue #119
The conventional changelog spec mentions that commit prefixes should be case insensitive: https://www.conventionalcommits.org/en/v1.0.0/# ...
Read more >Configuration file name case-sensitive?
Hello Splunk, Found a question about folder case-sensitivity and file content sensitivity, what about the file names, exp indexes.conf vs INDEXES.
Read more >Why are URLs case-sensitive?
URLs are not case-sensitive, only parts of them. For example, nothing is case-sensitive in the URL https://google.com ,.
Read more >Failed to copy configuration to working-config; reason ...
Make a determination of the Web Application Security (ASM) policy containing the correct case-sensitive value. The *only* way to change the case ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yup, I’ve come to that conclusion directly after I hit comment. Nice!
I have verified that this is no longer a problem. Everything is now case insensitive.