Fix missing triple``` characters in markdown-features.mdx#9694
Fix missing triple``` characters in markdown-features.mdx#9694heysokam wants to merge 1 commit intofacebook:mainfrom heysokam:patch-1
Conversation
|
Hi @heysokam! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
✅ [V2]Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
⚡️ Lighthouse report for the deploy preview of this PR
|
|
thanks for reporting the problem However it's technically impossible for me to merge if you don't sign the CLA, so let me know if you want to proceed. Otherwise I'll open another pr myself. |
|
Going to open another pr based on yours because cla is not signed and I have other tiny edits to the template to make BTW using indentation doesn't work anymore for code blocks, cf the result of your PR still not looking great: 
|
|
will be fixed in #9696 and you'll be credited |
3 participants
Sorry to be blunt, but I'm not gonna spend +1-2h reading the PR rules just to send such a simple fix.
I'm just fixing missing ``` characters.
Take it or leave it. I don't care either way.
Feel free to fix this in the proper way in a different PR or something, and remove/close this one, if the rules are strict enough for this to not be allowed at all.
Erroring output, without ```
Expected output, with ```
