<commit_before>---
title: Getting Started With Codeship Pro Part 3
layout: page
weight: 13
tags:
  - docker
  - jet
  - codeship pro
  - introduction
  - getting started
  - tutorial
  - getting started jet
category: Getting Started
redirect_from:
  - /docker-guide/getting-started-part-three/
---

The source for the tutorial is available on Github as [codeship/ci-guide](https://github.com/codeship/ci-guide/) and you can clone it via

```bash
git clone <EMAIL>:codeship/ci-guide.git
```

## Getting Started With Codeship Pro (Part 3)

Now that you have a working CI process with a successful test, the next step is to push out your Docker image!

## Required Services Before We Push

### A Codeship Account With Access To Codeship Pro

The first thing you'll need is a working Codeship account with a Codeship Pro project (**Codeship Pro is now free for 100 builds per month, 1 concurrent build, unlimited projects and unlimited users**). 
When creating your new project, make sure to select Codeship Pro after choosing the repo you're using.

![Selecting Codeship Pro]({{ site.baseurl }}/images/gettingstarted/setup_select_docker.png)

If you don't have a repo configured, just create a new repo on Github and push the code examples we've been using so far.

### An Image Registry Account

Now, you're also gonna need an image repo account. For this example, we're gonna go with Dockerhub but you could use Quay.io or your own self-hosted image repo.

## Let's Do A Push

Now that we have our accounts created, let's go ahead and open up our `codeship-steps.yml` file. After our test step, we're going to add a new step - a `push` step.<commit_msg>updating header to remove account reference<commit_after>---
title: Getting Started With Codeship Pro Part 3
layout: page
weight: 13
tags:
  - docker
  - jet
  - codeship pro
  - introduction
  - getting started
  - tutorial
  - getting started jet
category: Getting Started
redirect_from:
  - /docker-guide/getting-started-part-three/
---

The source for the tutorial is available on Github as [codeship/ci-guide](https://github.com/codeship/ci-guide/) and you can clone it via

```bash
git clone git@github.com:codeship/ci-guide.git
```

## Getting Started With Codeship Pro (Part 3)

Now that you have a working CI process with a successful test, the next step is to push out your Docker image!

## Required Services Before We Push

### A Codeship Pro Project

The first thing you'll need is a working Codeship account with a Codeship Pro project (**Codeship Pro is now free for 100 builds per month, 1 concurrent build, unlimited projects and unlimited users**). 
When creating your new project, make sure to select Codeship Pro after choosing the repo you're using.

![Selecting Codeship Pro]({{ site.baseurl }}/images/gettingstarted/setup_select_docker.png)

If you don't have a repo configured, just create a new repo on Github and push the code examples we've been using so far.

### An Image Registry Account

Now, you're also gonna need an image repo account. For this example, we're gonna go with Dockerhub but you could use Quay.io or your own self-hosted image repo.

## Let's Do A Push

Now that we have our accounts created, let's go ahead and open up our `codeship-steps.yml` file. After our test step, we're going to add a new step - a `push` step.
{'fraction_non_alphanumeric': 0.0753693096171239, 'fraction_numerical': 0.00482363581549593, 'mean_word_length': 3.9596412556053813, 'pattern_counts': {'":': 0, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 1, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4146986', 'n_tokens_mistral': 1000, 'n_tokens_neox': 915, 'n_words': 480}