This repository has been archived by the owner on Aug 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 340
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'scaleracademy:main' into cy2000yadav-details
- Loading branch information
Showing
2 changed files
with
40 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
## Welcome to Challenge 20 | ||
|
||
Welcome to the 20th Challenge | ||
|
||
Today you will learn about project boards on GitHub | ||
|
||
### What are Github Project Boards? | ||
|
||
GitHub project boards helps you keep track of stuffs you're actively working on within your repository. You can say it's a project managemnet tool, or even a collaboration tool for teams. You create a project board with columns for your TODO or backlogs or even bugs, In progress activies and lastly a column for your finished tasks. You can sort of see it as a SCRUM board. To learn more [about project boards go through this link](https://help.github.com/en/github/managing-your-work-on-github/about-project-boards) | ||
|
||
## Tasks | ||
|
||
- Create a GitHub repository for any project you can think up | ||
- On a sheet of paper create a TODO list (or backlog) of features you want to have in you app | ||
- Create a project board with a `TODO` column, `In progress`, `Done` | ||
- Create a card for all the items you already wrote on the sheet of paper in the TODO column | ||
- Work on the features synchronously and move the card respectively for each in progress task to the `In progress` column | ||
- When you're done with the `In progress` task move the card to the `Done` column | ||
|
||
## How to submit your entry | ||
|
||
- Take a screenshot of your project board for when you moved an card from `In progress` to `Done` | ||
- Add you screenshot to the Github issue created in the previous challenges |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
## Welcome to Challenge 21 | ||
|
||
Welcome to the 21st Challenge | ||
|
||
Today we will be learning about Git Aliases! :). This is an amazing feature that helps us use less keystroke | ||
|
||
The term alias is synonymous with a shortcut. Alias creation is a common pattern found in other popular utilities like `bash` shell. Aliases are used to create shorter commands that map to longer commands. Aliases enable more efficient workflows by requiring fewer keystrokes to execute a command. To learn more; | ||
|
||
- [Git Alias](https://www.atlassian.com/git/tutorials/git-alias) | ||
|
||
## Tasks | ||
|
||
- Go through the Git Alias documentation shared here | ||
- Create at least 2 alias for any git commands you feel is too long | ||
- Take a screenshot of the alias you created. hint run `git config --get-regexp alias` | ||
- Take a screenshot of using your alias | ||
- Post these screenshot in the issue created in the prior challenges |