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.
Wrong message when finishing a feature
See original GitHub issueI am getting the message below on Event Log:
5:20 PM XXX-15: The feature branch 'feature/XXX-15' was merged into 'null'
When finished I am into develop.
In my ./.git/config I have:
...
[gitflow "branch"]
master = master
develop = develop
[gitflow "prefix"]
feature = feature/
release = release/
hotfix = hotfix/
support = support/
versiontag = v
Similar: #129 - Wrong message when finishing a feature
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Get word suggestions & fix mistakes - Android - Messages Help
On your Android phone or tablet, open any app that you can type with, like Gmail or Keep. Tap where you can enter...
Read more >iOS 16: How to Unsend and Edit Text Messages on Your iPhone
Whether you made a typo or your message contains incorrect data, the editing feature is a nice way to make your corrections quickly....
Read more >iPhone Messages: 12 texting tips you didn't know ... - USA Today
Make it harder to respond to the wrong message To avoid embarrassing miscommunications, you can organize your group-texts by giving them ...
Read more >Sent an email by mistake? Here's what you need to do
then 'See all settings'. Next to 'Undo Send', select a Send cancellation period of 5, 10, 20, or 30 seconds.
Read more >How to use Auto-Correction and predictive text on your iPhone ...
Auto-Correction uses your keyboard dictionary to spellcheck words as you type, automatically correcting misspelled words for you.
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
As it happens the solution was to flip two lines. Seriously. Some bugs are like that - long time to debug, no time to resolve. Fix in 0.7.0, once that’s out
I finally figured out why this happens. Turns out that the reason is that because reading the gitflow config (where the info about the base branch is saved) is IO bound, by the time the message is displayed the feature was already closed and so there is no information in the config file about it.