35 | Show all commits, starting with newest
36 |
37 |
38 |
39 | Who changed what and when in a file
40 |
41 |
42 |
Branches and tags
43 |
44 | List all existing branches
45 |
46 |
47 |
48 | Switch HEAD branch
49 |
50 |
51 |
Update and publish
52 |
53 | List all currently configured remotes
54 |
55 |
56 |
57 | Download changes and merge into HEAD
58 |
59 |
60 |
61 | Publish local changes on a remote
62 |
63 |
64 |
Merge and rebase
65 |
66 | Merge branch into your current HEAD
67 |
68 |
69 |
70 | Rebase your current HEAD onto branch (not for published commits)
71 |
72 |
73 |
Undo
74 |
75 | Discard all local changes in working directory
76 |
77 |
78 |
79 | Discard local changes in a specific file
80 |
81 |
82 |
83 | Revert a commit
84 |
85 |
86 |
Setting up profile
87 |
88 | Using username
89 |
90 |
91 |
92 | Using email
93 |
94 |
95 |
96 | Checking you config settings
97 |
98 |
99 |
100 | )
101 |
102 | export default CheatSheet
103 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, sex characteristics, gender identity and expression,
9 | level of experience, education, socio-economic status, nationality, personal
10 | appearance, race, religion, or sexual identity and orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at rishabhbansal1855@gmail.com. All
59 | complaints will be reviewed and investigated and will result in a response that
60 | is deemed necessary and appropriate to the circumstances. The project team is
61 | obligated to maintain confidentiality with regard to the reporter of an incident.
62 | Further details of specific enforcement policies may be posted separately.
63 |
64 | Project maintainers who do not follow or enforce the Code of Conduct in good
65 | faith may face temporary or permanent repercussions as determined by other
66 | members of the project's leadership.
67 |
68 | ## Attribution
69 |
70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72 |
73 | [homepage]: https://www.contributor-covenant.org
74 |
75 | For answers to common questions about this code of conduct, see
76 | https://www.contributor-covenant.org/faq
77 |
--------------------------------------------------------------------------------
/src/pages/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 | import Link from 'gatsby-link'
3 | import Code from '../components/syntax'
4 |
5 | const IndexPage = () => (
6 |
7 |
Hello Developers!
8 |
Let's help you submit your first Pull Request.
9 |
Once your pull request is being merged, your profile will be visible in the Submissions
10 | section of this page. For this exercise you'll be adding a new entry to the source code of this website with your profile details.
11 | Excited? let's begin!
12 |
13 |
14 |
Step 1
15 |
16 | Goto the GitHub repository of this project and fork the project to your account.
17 | Click on the fork button on the top right corner of the repository page to do it. Once done, GitHub will take you to the forked copy in your account.
18 |
19 |
20 |
Step 2
21 |
22 | Clone the forked repository to your local machine. Click on the big green button saying "Clone or download" and copy the https url of your repository.
23 | Fire up the terminal (on linux systems ctrl+alt+t. on Windows open the Git-bash ) navigate to your desired directory and type the following command. Replace the link with the clone URL of your repository and hit Enter.
24 |
25 |
26 |
Step 3
27 |
28 | Let's start working on the changes required now! First cd into the cloned folder by typing the following command.
29 |
30 | Now, Before jumping in to the code, make sure you're working on a different branch and not in master. To create a new branch,
31 | from the terminal inside your current project directory type the following command.
32 |
33 | Replace the YOUR_USERNAME with your GitHub username or you can give any name to your branch which describes the purpose of the branch. Since here we're adding your profile,
34 | we'll simply give the name of the branch as above. eg: git branch rishabh-bansal-profile. Once you have created the new branch we'll change the current brach from master to your newly created branch.
35 | Execute the following command on your terminal.
36 |
37 |
38 |
Step 4
39 |
40 | In your file manager/terminal navigate to the downloaded repo. Open the sub-directory src/profiles/. and create a new .md file with your username as the filename with .md extension.
41 | It should look like YOUR_USER_NAME.mdeg: rishabh-bansal.md
42 | Open this file in your favourite editor and fill the details as below in the frontmatter of the markdown file.
43 |
44 | YOUR_USER_NAME.md
45 |
52 | Donot forget that the hyphens "---" are also part of the file. Once you finish adding the content, save the file.
53 |
54 |
55 |
Step 5
56 |
57 | Commit the changes with a suitable commit message. First we need to stage all the changes we made. Open the terminal inside the project directory and execute following commands.
58 |
59 | The above command stages all the changes, now lets commit it with a suitable message.
60 |
61 |
62 |
Step 6
63 |
64 | Let's push the changes to your repository! execute the following command to push all the changes to the forked copy in your GitHub account.
65 |
66 |
67 |
Step 7
68 |
69 | Now, open your web browser and goto the original repository on GitHub. If your changes has been pushed to your forked copy, You'll be able to see an option saying "New Pull Request" in the original repository.
70 | Click on the option, one next page choose the master branch of the main repo against your created-branch name ( choose your branch name we created and not master). the click on create pull request. Once you fill in the commit message and comment click on submit pull request.
71 | and you are all done! Wait for a reviewer to review your file and merge it to the master. Once its been successfully merged, your profile will be visible in the submissions tab.
72 |
![]({"https://avatars1.githubusercontent.com/"+username+"?size=200"}/)
6 |