Fork, Commit, Merge - Medium Issue (Markdown)

[nikohoffren]

Fork, Commit, Merge - Medium Issue (Markdown)

Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!

Description

Create a Markdown Guide

You need to modify guide.md file so it will function as a comprehensive Markdown guide. This guide should cover all aspects of Markdown, including headers, lists, links, images, code blocks, and tables.

How to get started

Open the tasks/markdown/medium directory from the root of your project.
Once the guide.md file is properly created as in the description, you are done and ready to make a pull request!
Note: You can test your Markdown code in a editor like this.

Check out README.md for more instructions and how to make a pull request.

Feel free to ask any questions here if you have some problems!

Also, kindly give this project a star to enhance its visibility for new developers!

[jonniie]

Hiii, would love to work on this 😁

[nikohoffren]

Hiii, would love to work on this 😁

Sure, go ahead!

[jonniie]

Great, you can assign the issue to me too 😁

[nikohoffren]

Great, you can assign the issue to me too 😁

No, as i explained in README these issues wont be assigned since they are always open and they are educational. After you are done with the issue, bot will revert the file back to previous state for the next contributor but you still get the commit.

But you are free to start solving!

[jonniie]

Alright, nice

…

On Wed, 2 Aug 2023, 04:46 Niko Hoffrén, ***@***.***> wrote: Great, you can assign the issue to me too 😁 No, as i explained in README these issues wont be assigned since they are always open and they are educational. After you are done with the issue, bot will revert the file back to previous state for the next contributor but you still get the commit. But you are free to start solving! — Reply to this email directly, view it on GitHub <#51 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARSLIGMO4SXAGMRDFLL72GTXTHESBANCNFSM6AAAAAA26JW7VI> . You are receiving this because you commented.Message ID: ***@***.***>