-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task 3: Some Markdown Styling #50
Comments
https://user-images.githubusercontent.com/48357016/79313830-9132e680-7f1e-11ea-8134-6d4c14a17d2e.PNG can you please help @lisa761 / @soumyaa1804 why am i getting this error! |
Can I start participating from today? |
@priyanka2109 Sure! Make sure you start from the first task and register in the form linked in the first task. |
Hi @mishra-aanchal Please create a new issue. It has been mentioned multiple times. |
Marking the end of 24 hours. |
In the last Task, you made your first PR by creating a markdown file. This Task of The Open Source Challenge will revolve around learning some nitty-gritties of the Markdown language. What you will do is take your
<name>.md
file, and add some amount of Markdown styling to show us how much of it you have grasped. Once done, you create a pull request to submit your task. Make sure you have completed Task 2 before moving ahead.The task is as follow:
Now, your fork must be pretty behind, since yesterday itself, we had a lot of merged pull requests. This is because when you update your main repository, it does not automatically update the forked repositories. For that, you have to manually update it. To see just how behind your repository is, go to your forked repository page on GitHub. You will see a message like
This branch is <some> commits behind ACM-IGDTUW:Master
.To update, follow these set of commands. Some of you must have done this in the previous task as well.
cd Open-Source-Challenge git checkout master git fetch upstream git rebase upstream/master git push origin master
For those who haven't had their previous PR merged, please skip the delete branch command, which is the
git branch -D <your-previous-branch-name>
command.Inside the project directory, run:
This creates a new branch. For example,
styling-md-john12
for us.To do so, you might want to add some extra information so that you can add styling to those. This information can be anything that you wish to add or are okay with everyone knowing about. For example, you could write some of your achievements.
You can refer to this Markdown Cheat-sheet for styling.
You may want to preview what your markdown code looks like after compilation, so you may start writing your code in this online markdown previewer, StackEdit and then when you are satisfied with the styling you can copy and paste your code into your markdown file.
Done! We will see your PR as a submission. This task will have an evaluation based on how well you have grasped Markdown. As one of the important factors of open source is to be able to find and do things on your own, this Task will be a great way to move in that direction.
Remember that any technical doubts will be answered only through the issues created in the repository. This is an important rule that you must follow.
The text was updated successfully, but these errors were encountered: