-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
11 changed files
with
17 additions
and
1 deletion.
There are no files selected for viewing
Empty file.
Empty file.
Empty file.
Empty file.
Empty file.
Empty file.
Empty file.
Empty file.
Empty file.
Empty file.
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 |
---|---|---|
@@ -1 +1,17 @@ | ||
# git-flow-exercise | ||
# Git Workflow Exercise | ||
For this exercise we will use [Github Flow](https://guides.github.com/introduction/flow/), a modified, lightweight version of [Git Flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow). | ||
|
||
## Instructions | ||
This repo contains answers to the collection of [Frontend Interview Questions](https://github.com/h5bp/Front-end-Developer-Interview-Questions#front-end-job-interview-questions) by the developers behind [H5BP](https://html5boilerplate.com/). | ||
|
||
1. Clone this repository. | ||
|
||
2. Choose an interview question to answer from [Frontend Interview Questions](https://github.com/h5bp/Front-end-Developer-Interview-Questions#front-end-job-interview-questions) | ||
|
||
3. Create and push a new feature branch that is named adequately to inform your team of which question you have chosen to answer. | ||
|
||
4. In the appropriate folder of your feature branch, create a [Markdown](https://guides.github.com/features/mastering-markdown/) file that contains the answer to your chosen question. The file should be named in the following format: `complete-text-of-question.md` | ||
|
||
5. Once you are finished, commit your changes and push your feature branch to the repository. | ||
|
||
6. Follow the instructions for submitting a pull request. |