I don't understand what this CR is intended to fix. Part of the original GH issue was that the app was changing the inputted markdown text. Rather than manually editing the article back to its original state (which is what this CR seems to be doing, in part), it seems to me that we should ensure the app simply doesn't auto-change it for us.
Are you trying to test whether the app will auto-change the inputted text if I accept your CR?
I don't understand what this CR is intended to fix. Part of the original GH issue was that the app was changing the inputted markdown text. Rather than manually editing the article back to its original state (which is what this CR seems to be doing, in part), it seems to me that we should ensure the app simply doesn't auto-change it for us.
Are you trying to test whether the app will auto-change the inputted text if I accept your CR?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on change requests or issues. Learn more about blocking a user.
I don't understand what this CR is intended to fix. Part of the original GH issue was that the app was changing the inputted markdown text. Rather than manually editing the article back to its original state (which is what this CR seems to be doing, in part), it seems to me that we should ensure the app simply doesn't auto-change it for us.
Are you trying to test whether the app will auto-change the inputted text if I accept your CR?
What do you mean it auto-changes it?
Problem 2: https://github.com/okTurtles/forkana/issues/262
It's not intended to fix anything except more testing.
Change request successfully merged and closed