See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
| package test | |
| import scala.concurrent.duration._ | |
| import io.gatling.core.Predef._ | |
| import io.gatling.http.Predef._ | |
| import io.gatling.jdbc.Predef._ | |
| class LoginTest extends Simulation { |
In order of first appearance in The Morning Paper.
This method avoids merge conflicts if you have periodically pulled master into your branch. It also gives you the opportunity to squash into more than 1 commit, or to re-arrange your code into completely different commits (e.g. if you ended up working on three different features but the commits were not consecutive).
Note: You cannot use this method if you intend to open a pull request to merge your feature branch. This method requires committing directly to master.
Switch to the master branch and make sure you are up to date:
#Introduction to Devops Resources:
##Chapter 1
2015 State of DevOps Report https://puppet.com/resources/white-paper/2015-state-of-devops-report
Knight Capital https://en.wikipedia.org/wiki/Knight_Capital_Group
#Getting Started
##Webpage:
<html>
<head>
<title>Testing with Ruby and Selenium WebDriver</title>
</head>
<body bgcolor="antiquewhite">