When using issue-flow I experience many times (probably due to mistakes I do) that issue branches ends up being marked as several commits ahead of main, though the code changes are actually implemented. What can we implement to help users prevent experiencing the same as me?
Also, many times there are left-overs in the .issueflows folder. I guess mostly within the 01-current-issues folder. Are there any things we can do to help that from happening that often?
When using issue-flow I experience many times (probably due to mistakes I do) that issue branches ends up being marked as several commits ahead of main, though the code changes are actually implemented. What can we implement to help users prevent experiencing the same as me?
Also, many times there are left-overs in the .issueflows folder. I guess mostly within the 01-current-issues folder. Are there any things we can do to help that from happening that often?