- π©βπ» Engineer @ Ushahidi
- π Building Collabo Community
- π Gender: ObΓ¬nrin l'α»lα»Μrun dΓ‘ mi
- π¬ Ask me about: Software Engineering, open source, collaboration and community
- π± What am I in tech exactly? Honestly I can't pinpoint. But I can tell you I'm evolving and discovering...
- β‘ Fun fact(s): I'm very organised, consistency is π―, and I love acoustic guitar
git-github-training's Introduction
git-github-training's People
git-github-training's Issues
Issue 2: Create a folder called "command-line" in the @Dkingofcode folder, and add readme file - more details in issue body
Note
Use the command line for this task.
Make sure to sync changes to your local and remote fork before you start this task.
Task description
- Create a folder called
command-line
in the @Dkingofcode folder - Create a readme file inside the
command-line
folder. - The content of the readme file must be exactly the same as what is in @Ifycode's readme file
Create github markdown section and youtube link section inside the README.md file found in the set2-folder
Task
Create github markdown section and youtube link section inside the README.md file found in the set2-folder
Add YouTube video link to readme help contributors know how to contribute using github UI
Task
- Watch this video to help you understand how to contribute a repo that is not yours.
https://youtu.be/2X1FjFqIwIY - After that, add a section called "How to submit your changes to this repo with Github UI" to the readme of this repo, and creatively add the above YouTube video link under the new section you created.
Issue 3: Edit section 1 of the readme inside @your-github-username-here/github-ui folder
Note
Once the instructor has created the scenario for conflicts to happen and has asked you to go ahead with this task, do not sync your fork. Check the develop branch of your fork is 1 commit behind the develop branch of the original repo. Then just go ahead with the task below.
Task description
- Go to section 1 of the readme inside @your-github-username-here/github-ui folder
- Change the text from "Watch this video" to "Just watch this video"
- Merge the conflict
- Add a comment in you pull request to let instructor know that your pull request is ready for review when you are done
Note
After you have sent a pull request for the above task, do not sync your fork. Check that the develop branch of your fork is still 1 commit behind the develop branch of the original repo. Then just go ahead to create another branch from develop and work on issue #97 immediately.
@oyenuga17 delete readme file
One more rinse and repeat task for @oyenuga17
Delete the readme file inside the @oyenuga17 folder that is not in any folder.
Issue 2: Create a folder called "command-line" in the @oyenuga17 folder, and add readme file - more details in issue body
Note
Use the command line for this task.
Make sure to sync changes to your local and remote fork before you start this task.
Task description
- Create a folder called command-line in the @oyenuga17 folder
- Create a readme file inside the command-line folder.
- The content of the readme file must be exactly the same as what is in @Ifycode's readme file
Issue 1: Create a folder called @samuko-things with a readme file in it - more details in issue body
Note
Use the GitHub UI for this task
Task description
Step 1:
- In this repository, create a folder called @samuko-things.
- This folder you created should have a readme file in it.
- The readme file you create should contain the title and description from @Ifycode's readme file.
- Commit your changes, and send a pull request.
- At this point, we are going to assume that @Ifycode has reviewed your pull request, and she left you this comment below:
Hi, Nice job! Also help add section 1 and section 2 from @Ifycode's readme file.
Step 2:
- Add section 1 and section 2 from @Ifycode's readme file.
- Commit your changes.
- At this point, we are again going to assume that @Ifycode has reviewed your pull request, and she left you this comment below:
Hmm... Ok, I change my mind. I would like us to add more structure to this project. Please follow step 3 below.
Step 3:
- Create a new folder inside the @samuko-things folder called github-ui. The new folder should contain a readme file.
- The content of the readme file inside the github-ui folder should be everything that is in @Ifycode's readme file.
- Commit your changes.
- At this point, we are again going to assume that @Ifycode has reviewed your pull request, and she left you this comment below:
You have done a very good job. But... You forgot to delete the readme file that is not in the github-ui folder.
Step 4:
- Delete the readme file inside the @samuko-things folder, that is not in any folder.
- Commit your changes.
- Tag @Ifycode in the comment on your pull request and let her know your PR is ready for a real review π
Helpful resources
Issue 4: Edit section 2 of the readme inside @oyenuga17/github-ui folder
Note
Remember do not sync your fork before you start the task below.
Task description
- Go to section 2 of the readme inside @oyenuga17 /github-ui folder.
- Change "This resource tells you how to format content using github markdown and you can also click this to download github markdown cheat sheet in pdf." to a list instead. Use the list below.
- Merge the conflict (see merge note below)
- Add a comment in you pull request to let instructor know that your pull request is ready for review when you are done
Note
Merge note: At the point when you are merging the conflict, the changes should contain the text "The resources below show you how to use markdown:" and the new list you added.
Issue 4: Edit section 2 of the readme inside @your-github-username-here/github-ui folder
Note
- Remember do not sync your fork before you start the task below.
- Use github-ui for this task
Task description
- Go to section 2 of the readme inside @your-github-username-here/github-ui folder.
- Change "This resource tells you how to format content using github markdown and you can also click this to download github markdown cheat sheet in pdf." to a list instead. Use the list below.
- Merge the conflict (see merge note below)
- Add a comment in you pull request to let instructor know that your pull request is ready for review when you are done
Note
Merge note: At the point when you are merging the conflict, the changes should contain the text "The resources below show you how to use markdown:" and the new list you added.
Create a folder inside the @Dkingofcode folder called "github-ui" containing a readme file that has content
For @Dkingofcode since you had plenty issues with Monday's tasks.
Description:
- Create a new folder inside the @Dkingofcode folder called
github-ui
. The new folder should contain a readme file. - The content of the readme file inside the github-ui folder should be everything that is in the readme file you previously created in the @Dkingofcode folder.
Create a folder inside the @Danbaba1 folder called "github-ui" containing a readme file that has content
For @Danbaba1 just for rinse and repeat sake.
Description:
Issue 2: Create a folder called "command-line" in the @your-github-username-here folder, and add readme file - more details in issue body
Note
Use the command line for this task.
Make sure to sync changes to your local and remote fork before you start this task.
Task description
- Create a folder called
command-line
in the @your-github-username-here folder - Create a readme file inside the
command-line
folder. - The content of the readme file must be exactly the same as what is in @Ifycode's readme file
Dummy issue
- Dummy issue
Create github markdown section and youtube link section inside the README.md file found in the set1-folder
Task
Create github markdown section and youtube link section inside the README.md file found in the set1-folder
Github UI (set 1) Task 1b: Add more content to the readme file inside @Danbaba1 folder
Task description
- add the How to submit your changes to this repo with Github UI section from @Ifycode's readme file.
Add github markdown section and links to readme
Task
Add a section titled "Github markdown resources". In this section tell the reader that this resource: https://gist.github.com/cuonggt/9b7d08a597b167299f0d will show them how to format content using github markdown. Also let them know that they can download github markdown cheat sheet in pdf by clicking on this link: https://ifycode.github.io/git-github-training/markdown-cheatsheet.pdf
Note: Add this new section before the contributors section, in the readme.
Github UI (set 1) Task 1a: Create a folder called @Danbaba1 with a readme file in it containing content
Task description
- In this repository, create a folder called @Danbaba1.
- This folder you created should have a readme file in it.
- The readme file you create should contain the heading and description from @Ifycode's readme file.
Helpful resources
Issue 5: Edit section 1 and section 2 of the readme inside @oyenuga17/command-line folder
Note
Once the instructor has created the scenario for conflicts to happen and has asked you to go ahead with this task, do not sync your fork. Check the develop branch of your fork is 1 commit behind the develop branch of the original repo. Then just go ahead with the task below.
Task description
- Go to section 1 of the readme inside @oyenuga17 /command-line folder
- Change the text from "Watch this video" to "Just watch this video"
- Go to section 2 of the readme inside @oyenuga17 /command-line folder.
- Change "This resource tells you how to format content using github markdown and you can also click this to download github markdown cheat sheet in pdf." to a list instead. Use the list below.
- Merge the conflict (just as you have been taught)
- Add a comment in you pull request to let instructor know that your pull request is ready for review when you are done
Issue 2: Create a folder called "command-line" in the @Danbaba1 folder and add readme file - more details in issue body
Note
Use the command line for this task.
Make sure to sync changes to your local and remote fork before you start this task.
Task description
- Create a folder called command-line in the @Danbaba1 folder
- Create a readme file inside the command-line folder.
- The content of the readme file must be exactly the same as what is in @Ifycode's readme file
Change your folder name from set-1 to your github username through the github UI
@oyenuga17, you added the set-1 folder so this task is for you.
Task description
Change your folder name from set-1 to your github username @oyenuga17
through the github UI.
Helpful resource
Issue 1: Create a folder called @your-github-username-here with a readme file in it - more details in issue body
Note
- Use the GitHub UI for this task
- Create your own issue with this template
- Change @your-github-username-here to your own Github username everywhere it occurs in your own issue
- Instead of having to type out this long template just copy and paste it from the comment below.
Task description
Step 1:
- In this repository, create a folder called @your-github-username-here.
- This folder you created should have a readme file in it.
- The readme file you create should contain the title and description from @Ifycode's readme file.
- Commit your changes, and send a pull request.
- At this point, we are going to assume that @Ifycode has reviewed your pull request, and she left you this comment below:
Hi, Nice job! Also help add section 1 and section 2 from @Ifycode's readme file.
Step 2:
- Add section 1 and section 2 from @Ifycode's readme file.
- Commit your changes.
- At this point, we are again going to assume that @Ifycode has reviewed your pull request, and she left you this comment below:
Hmm... Ok, I change my mind. I would like us to add more structure to this project. Please follow step 3 below.
Step 3:
- Create a new folder inside the @your-github-username-here folder called github-ui. The new folder should contain a readme file.
- The content of the readme file inside the github-ui folder should be everything that is in @Ifycode's readme file.
- Commit your changes.
- At this point, we are again going to assume that @Ifycode has reviewed your pull request, and she left you this comment below:
You have done a very good job. But... You forgot to delete the readme file that is not in the github-ui folder.
Step 4:
- Delete the readme file inside the @your-github-username-here folder, that is not in any folder.
- Commit your changes.
- Tag @Ifycode in the comment on your pull request and let her know your PR is ready for a real review π
Helpful resources
Create a folder called set 2 and a file in it containing the Repo heading/title and the description
Task: Create a folder called set 2 and a file in it. The name of the file should be README.md. This readme file should contain the Repo heading/title and the description.
Task: Create a folder called set 2 and a file in it. The name of the file should be README.md. This readme file should contain the Repo heading/title and the description.
Symbols are used in place of words in repo readme
Symbols are used in place of words in repo readme. For example "and" is written as &.
Change your folder name from set-2 to your github username through the github UI
@Dkingofcode, you added the set-2 folder so this task is for you.
Task description
Change your folder name from set-2 to your github username @Dkingofcode
through the github UI.
Helpful resource
https://debug.to/1088/how-to-change-folder-name-in-github
Issue 5: Edit section 1 and section 2 of the readme inside @your-github-username-here/command-line folder
Note
Once the instructor has created the scenario for conflicts to happen and has asked you to go ahead with this task, do not sync your fork. Check the develop branch of your fork is 1 commit behind the develop branch of the original repo. Then just go ahead with the task below.
Task description
- Go to section 1 of the readme inside @your-github-username-here/command-line folder
- Change the text from "Watch this video" to "Just watch this video"
- Go to section 2 of the readme inside @your-github-username-here/command-line folder.
- Change "This resource tells you how to format content using github markdown and you can also click this to download github markdown cheat sheet in pdf." to a list instead. Use the list below.
- Merge the conflict (see merge note below)
- Add a comment in you pull request to let instructor know that your pull request is ready for review when you are done
Create a folder called set 1 and a file in it containing the Repo heading/title and the description
Task:
Create a folder called set 1 and a file in it. The name of the file should be README.md. This readme file should contain the Repo heading/title and the description.
Create a folder inside the @oyenuga17 folder called "github-ui" containing a readme file that has content
For @oyenuga17 just for rinse and repeat sake.
Description:
- Create a new folder inside the @oyenuga17 folder called
github-ui
. The new folder should contain a readme file. - The content of the readme file inside the github-ui folder should be everything that is in the readme file you previously created in the @oyenuga17 folder.
Github UI (set 1) Task 2: Create a folder called @Danbaba1 with a readme file in it containing all content
Task description
- In this repository, create a folder called @Danbaba1.
- This folder you created should have a readme file in it.
- The readme file you create should contain all the content inside @Ifycode's readme file.
- Make sure to use markdown to format the file content.
Helpful resources
Issue 3: Edit section 1 of the readme inside @oyenuga17/github-ui folder
Note
Once the instructor has created the scenario for conflicts to happen and has asked you to go ahead with this task, do not sync your fork. Check the develop branch of your fork is 1 commit behind the develop branch of the original repo. Then just go ahead with the task below.
Task description
- Go to section 1 of the readme inside @oyenuga17 /github-ui folder
- Change the text from "You can watch this video" to "Just watch this video"
- Merge the conflict
- Add a comment in you pull request to let instructor know that your pull request is ready for review when you are done
Note
After you have sent a pull request for the above task, do not sync your fork. Check that the develop branch of your fork is still 1 commit behind the develop branch of the original repo. Then just go ahead to create another branch from develop and work on issue #97 immediately.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.