Managing merge conflicts shows duplicate steps 10/11 and never completes 11

It also seems to think there is a step 12 for setting up GitHub pages, when the results page below suggests that as an optional next step

Hi @mungojam! It looks like your repository is functioning well, but the screen on wasn’t showing what you’d expected. Is that correct? If so, if you go back now and refresh, is it showing the updated steps? 

If not, I’ll pass this along to our engineering team. Thanks for letting us know! 

Hi @brianamarie, that’s correct. But the screen on is still showing as per my screenshot so there’s still an issue 

@mungojam Thanks for confirming. I’ll pass this along to our engineering team, and hopefully we’ll be able to get to the bottom of this quickly. 

Hi @mungojam! We’ve reset your steps, so you should be good to go. The one thing that is possibly missing from your side is that it doesn’t appear that you’ve enabled GitHub Pages. Once you do that, you should be back on track. Let me know if you have more questions! :smiley:

Thanks @brianamarie, that has removed the duplicate step. I had already enabled GitHub pages in an attempt to resolve the issue before (though there was the duplicate step in between so I didn’t expect it to fix it):

I’ve now just tried turning pages off and on again, but that didn’t help either.

1 Like

There is also still an inconsistency in the final bot post as to whether enabling Pages is an optional step or not:

1 Like

Hi @mungojam and @brianamarie I have exactly the same issue mylelf.

Would love to know what to do to resolve the issue.


Hey @mungojam & @cristytarantino!

Thank you both for reporting this issue :heart: We’ve deployed some fixes, and you shouldn’t see the extra “turn on GitHub Pages” step anymore. Please let us know if you’re still seeing a problem!

Thanks again!


1 Like