Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time
# Git Workflow Exercise
For this exercise we will use [Github Flow](https://help.github.com/en/articles/github-flow), a modified, lightweight version of [Git Flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
GitHub Flow is a simple and effective branching strategy which the folks at GitHub use. Most teams actually do not need everything Git Flow gives them and are much better off with a simpler 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. Fork this repository.
2. Choose a previously unanswered interview question from [Frontend Interview Questions](https://github.com/h5bp/Front-end-Developer-Interview-Questions#front-end-job-interview-questions) <u>or</u> improve upon an existing answer in one of the markdown (*.md) files.
3. Create a new feature branch that is named in the format of `feature/description-of-feature`. For example, if you might name your branch `feature/describing-floats` if answering a question about floats.
4. In the appropriate file, using [Markdown](https://guides.github.com/features/mastering-markdown/), supply the answer to your chosen question.
5. Once you are finished, commit your changes and push your feature branch to the repository.
6. Follow the instructions for submitting/sending a [pull request](https://help.github.com/en/articles/creating-a-pull-request) to the owner of the repository.
## Table of Contents
1. [General](general.md)
1. [HTML](html.md)
1. [CSS](css.md)
1. [JavaScript](javascript.md)