├── .github
├── ISSUE_TEMPLATE
│ └── add-myself-as-learner---.md
├── issues_labeler.yml
└── workflows
│ ├── blank.yml
│ ├── greet.yml
│ ├── greeting.yml
│ ├── issue_labeler.yml
│ └── labels.yml
├── .vs
└── slnx.sqlite
├── CODE_OF_CONDUCT.md
├── LICENSE
├── README.md
├── Tribute_To_Contributors.html
├── _config.yml
├── clone.png
├── commit.png
├── createPR.png
├── creating_repository.md
├── fork.png
├── git
├── index.css
├── index.html
├── labels.json
├── newPR.png
├── pullrequest.png
├── push.png
├── stagechanges.png
└── vscode.png
/.github/ISSUE_TEMPLATE/add-myself-as-learner---.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Add Myself as Learner !!
3 | about: Add My Info Box in index.html
4 | title: Learner Addition
5 | labels: "⭐ goal: addition, \U0001F7E7 priority: high"
6 | assignees: ''
7 |
8 | ---
9 |
10 | Enter Details Below !
11 |
12 | Github Username :-
13 | Your Name :-
14 |
15 | Thanks !!!
16 |
--------------------------------------------------------------------------------
/.github/issues_labeler.yml:
--------------------------------------------------------------------------------
1 |
2 | good first issue:
3 | - "( C )"
4 | C-Plus-Plus:
5 | - "(C-Plus-Plus|CPP|cpp)"
6 | C-Sharp:
7 | - "(C-Sharp|csharp|C#)"
8 | Go:
9 | - "(Go|GO|Golang)"
10 | Java:
11 | - "(Java|java)"
12 | JavaScript:
13 | - "(JavaScript|JAVASCRIPT|Javascript|javascript|JS|js)"
14 | Python:
15 | - "(Python|PYTHON|python)"
16 | Q-Sharp:
17 | - "(Q-Sharp|qsharp|Q#)"
18 | enhancement:
19 | - "(enhancement)"
20 | trial:
21 | - "(trial)"
22 |
--------------------------------------------------------------------------------
/.github/workflows/blank.yml:
--------------------------------------------------------------------------------
1 | name: Greetings
2 |
3 | on: [pull_request_target, issues]
4 |
5 | jobs:
6 | greeting:
7 | runs-on: ubuntu-latest
8 | steps:
9 | - uses: actions/first-interaction@v1
10 | with:
11 | repo-token: ${{ secrets.GITHUB_TOKEN }}
12 | issue-message: "Hi👋 thanks for creating an issue on my Readme Profile !!, Will get back to you soon !! Your Contribution matters a lot for me ! "
13 | pr-message: "🎉Congratulations!!🎉 for making PR , I will review it soon !! Your Contribution matters a lot for me !"
14 |
--------------------------------------------------------------------------------
/.github/workflows/greet.yml:
--------------------------------------------------------------------------------
1 | name: Greetings
2 |
3 | on: [pull_request_target, issues]
4 |
5 | jobs:
6 | greeting:
7 | runs-on: ubuntu-latest
8 | steps:
9 | - uses: actions/first-interaction@v1
10 | with:
11 | repo-token: ${{ secrets.GITHUB_TOKEN }}
12 | issue-message: "Hi👋 thanks for creating an issue on my Readme Profile !!, Will get back to you soon !! Your Contribution matters a lot for me ! "
13 | pr-message: "🎉Congratulations!!🎉 for making PR , I will review it soon !! Your Contribution matters a lot for me !"
14 |
--------------------------------------------------------------------------------
/.github/workflows/greeting.yml:
--------------------------------------------------------------------------------
1 | name: Greetings
2 |
3 | on: [pull_request_target, issues]
4 |
5 | jobs:
6 | greeting:
7 | runs-on: ubuntu-latest
8 | steps:
9 | - uses: actions/first-interaction@v1
10 | with:
11 | repo-token: ${{ secrets.GITHUB_TOKEN }}
12 | issue-message: "Hi👋 thanks for creating an issue on my Readme Profile !!, Will get back to you soon !! Your Contribution matters a lot for me ! "
13 | pr-message: "🎉Congratulations!!🎉 for making PR , I will review it soon !! Your Contribution matters a lot for me !"
--------------------------------------------------------------------------------
/.github/workflows/issue_labeler.yml:
--------------------------------------------------------------------------------
1 |
2 | name: Issues Labeler
3 | on:
4 | issues:
5 | types: [opened, edited]
6 | pull_request_target:
7 | types: [opened, reopened, edited, closed, synchronize]
8 | jobs:
9 | labeler:
10 | runs-on: ubuntu-latest
11 | steps:
12 | - uses: github/issue-labeler@v2.0
13 | with:
14 | repo-token: "${{ secrets.GITHUB_TOKEN }}"
15 | configuration-path: .github/issues_labeler.yml
16 | enable-versioned-regex: 0
17 |
--------------------------------------------------------------------------------
/.github/workflows/labels.yml:
--------------------------------------------------------------------------------
1 | name: Import open source standard labels
2 |
3 | on:
4 | push:
5 | branches: [ main ]
6 |
7 | jobs:
8 | labels:
9 |
10 | runs-on: ubuntu-latest
11 |
12 | steps:
13 | - uses: actions/setup-node@v2
14 | with:
15 | node-version: '14'
16 | - uses: EddieHubCommunity/gh-action-open-source-labels@v0.2.2
17 | with:
18 | github-token: ${{ secrets.GITHUB_TOKEN }}
19 | owner-name: ${{ github.repository_owner }}
20 | repository-name: ${{ github.event.repository.name }}
21 |
--------------------------------------------------------------------------------
/.vs/slnx.sqlite:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rohan-kulkarni-25/Learn-GITHUB/fbb60024f56eeecbfb2161c37dd8d74fb9f909cb/.vs/slnx.sqlite
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | rohank2502@gmail.com.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
129 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2021 Rohan Kulkarni
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
You Should see your entered name and email under `user.name` & `user.email`
32 |
33 |
34 |
35 |
36 |
Setting Project on Local System :-
37 |
38 |
Fork the Repository of Project
39 |
40 | ( You will see this on Top Right of Github Repository !)
41 |
Clone the Repository
42 |
43 | ( Click on the Green Code button and Copy the link `https://github.com/........` )
44 |
Open Git bash where you want to clone the project ( Avoid On Desktop )
45 |
Run Command
46 |
47 | `git clone link`
48 |
49 | (In Place of link paste the link you copied)
50 |
51 |
Project Cloned in System
52 |
53 |
54 |
55 |
Using Vs-Code for Working on Project
56 |
57 |
58 |
Don't Forget to Pull Before making Commit this will avoid merge conflicts
59 |
After Making certain amount of changes you can save the changes by `CTRL + S` 😅
60 |
Stage the changes
61 |
62 | (Stage All Changes)
63 |
Commit Changes
64 |
65 | (Commit Staged)
66 |
Push Changes
67 |
68 | (Push)
69 |
70 |
71 |
72 |
Creating Pull Request on Github
73 |
74 |
Go in Pull Request Section
75 |
76 |
Create New Pull Request
77 |
78 |
Create New Pull Request
79 |
80 |
Add Title, Description & Create Pull Request
81 |
That's It You have Succesfully Created a Pull Request
82 |
83 |
84 |
HAND-ON DEMO
85 |
86 |
As you have learned to fork, clone, make changes and also to push those changes and even we learned to create Pull request !
87 |
88 |
Now You have one Task to do !!
89 |
You have to create a issue. You will get option to create a issue as `Add Myself as Learner !!`
There is one file index.html you have to copy the text given below and paste the code in file !!
90 |
91 |
After the src in image tag there is my username `rohan-kulkarni-25` In place of that you have to add your github username !! Make sure there is `.png` after you enter your username !! Also Enter you name In place of mine inside the `P` tag !! Paste the edited content in index.html as per the sequence above the line `Paste here`
92 |
93 |
You have to create a Pull Request and add `Fixes #IssueNumber` in description !! Issue number is the number of issue you created !
104 | MADE WITH ❤️ BY ROHAN KULKARNI Get Connected
105 |
127 |
128 |
129 |
130 |
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | theme: jekyll-theme-cayman
--------------------------------------------------------------------------------
/clone.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rohan-kulkarni-25/Learn-GITHUB/fbb60024f56eeecbfb2161c37dd8d74fb9f909cb/clone.png
--------------------------------------------------------------------------------
/commit.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rohan-kulkarni-25/Learn-GITHUB/fbb60024f56eeecbfb2161c37dd8d74fb9f909cb/commit.png
--------------------------------------------------------------------------------
/createPR.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rohan-kulkarni-25/Learn-GITHUB/fbb60024f56eeecbfb2161c37dd8d74fb9f909cb/createPR.png
--------------------------------------------------------------------------------
/creating_repository.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | ONCE YOU HAVE LOG ON TO YOUR GITHUB ACCOUNT
4 |
5 | NOW TO LEARN HOW TO CREATE YOUR OWN REPOSITORY
6 |
7 | follow the below steps ( all this need only your dedication and belive so take a chill pill )
8 |
9 | STEP 1- click on new or the plus symbol ( take all this like a hide and seek game and find all new icon as you are advised )
10 | STEP 2- name your repository [ make sure that your file name should be of proper extention ,now think about an awesome name ]
11 | STEP 3- disrcription is not require as you are biginner so take a deep breadth and procced to next.
12 | STEP 4- choose public option [ Actually if you have paid plan then only you can choose private ]
13 | STEP 5- you can initialize with or without readme file it's all up to you [ if you want to choose readme file just select the option ,as you will sellect ,
14 | you will see a click mark over there ,nothing more to do]
15 | STEP 6- then click on create repository [ you will get your repository with your given name ]
16 | STEP 7- create new file [ this option may you get inside an file option , believe me eveerything is in front of you , it's the time to know your passion and pataince ]
17 | STEP 8- now name the file [ I DON'T WANT TO CONFUSE YOU SO , for example (name.txt), like this you can write your file name]
18 | STEP 9- now write whatever you want to write in the file (ex- about yourself, one day diary, how you learn github etc. )
19 | STEP 10- write whatever you want to write in commit new file ( for example file created )
20 | STEP 11- commit to master brench file option will be there ,remain that option as default for now.
21 | STEP 12- click on commit new file (you will see your file with readme file over there )
22 | STEP 13- click on edit (if you want to change something or update the file ,and repeat the proceed, again you can commit your edited things to the main branch for now )
23 |
24 |
25 | {YOU CAN GO TO COMMIT OPTIONS AND SEE WHATEVER YOU HAVE COMMITTED}
26 |
27 | I HOPE ALL THIS IS HELPFUL
28 | HAVE A GREAT DAY GUYS ALWAYS , ENJOY .
29 |
--------------------------------------------------------------------------------
/fork.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rohan-kulkarni-25/Learn-GITHUB/fbb60024f56eeecbfb2161c37dd8d74fb9f909cb/fork.png
--------------------------------------------------------------------------------
/git:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rohan-kulkarni-25/Learn-GITHUB/fbb60024f56eeecbfb2161c37dd8d74fb9f909cb/git
--------------------------------------------------------------------------------
/index.css:
--------------------------------------------------------------------------------
1 | .head{
2 | text-align: center;
3 | font-size: 5vmin;
4 | }
5 |
6 | .subhead{
7 | text-align: center;
8 | font-size: 3vmin;
9 | }
10 |
11 | .header{
12 | background-color: skyblue;
13 | padding: 2vmin;
14 | }
15 |
16 | .avatar{
17 | width:40vmin;
18 | padding-bottom: 0%;
19 | margin-bottom: 0%;
20 |
21 | }
22 |
23 | body{
24 | background-color: goldenrod;
25 |
26 | }
27 |
28 |
29 |
30 |
31 | .individual {
32 | margin: 2vmin;
33 | display: inline-flex ;
34 | border-radius: 2vmin;
35 | border: 3vmin;
36 | border-style: solid;
37 | border-color: rgb(255, 255, 255);
38 |
39 | width: max-content;
40 | }
41 |
42 |
43 |
44 | .name{
45 | font-size: 4vmin;
46 | text-align: center;
47 | background-color: white;
48 | margin-top: 0%;
49 | padding: 2vmin;
50 | padding-bottom: 0;
51 | margin-bottom: 0%;
52 | }
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 | LEARN-GITHUB | HANDS-ON DEMO
9 |
10 |
11 |
12 |
13 |
LEARN-GITHUB | HANDS-ON DEMO
14 |
15 | Yes we all have Learned to do Basic Operation with Github + Vs Code !!
16 |
76 | 
78 | 
80 | 
`
100 | `
114 | 
115 |
116 | 
23 | 
33 | 
40 | 
50 | 
57 | 
64 | 
71 | 
78 | 
85 | 
92 | 
99 | 
106 | 
113 | 
120 | 
127 | 
137 | 
144 | 
154 | 
161 | 
170 | 
176 | 
183 | 
193 | 
199 | 
206 | 
215 | 
223 |