Skip to content

Commit

Permalink
initial organization
Browse files Browse the repository at this point in the history
  • Loading branch information
bpd01001 committed Apr 11, 2019
1 parent 557598a commit 72d5147
Show file tree
Hide file tree
Showing 11 changed files with 17 additions and 1 deletion.
Empty file added 01 - General/.gitkeep
Empty file.
Empty file added 02 - HTML/.gitkeep
Empty file.
Empty file added 03 - CSS/.gitkeep
Empty file.
Empty file added 04 - JS/.gitkeep
Empty file.
Empty file added 05 - Accessibility/.gitkeep
Empty file.
Empty file added 06 - Testing/.gitkeep
Empty file.
Empty file added 07 - Performance/.gitkeep
Empty file.
Empty file added 08 - Network/.gitkeep
Empty file.
Empty file added 09 - Coding/.gitkeep
Empty file.
Empty file added 10 - Fun/.gitkeep
Empty file.
18 changes: 17 additions & 1 deletion README.md
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.

0 comments on commit 72d5147

Please sign in to comment.