Skip to main content
In Sprint-01, you’ll lay the groundwork for your DevOps pipeline by:
  1. Creating and configuring a GitHub repository.
  2. Applying organizational best practices (branching strategy, repository settings).
  3. Writing a sample Dockerfile and building the image.
  4. Running and testing the Docker image locally.
The image shows the number "04" and the text "Testing the code locally" with a simple icon of code lines inside a circle.
  1. Pushing the tested code and Docker image to GitHub.
The image shows the number "05" and an icon of the GitHub logo with an arrow, accompanied by the text "Pushing the code to the GitHub repo."
  • A GitHub account with SSH keys configured
  • Docker installed locally
  • Git CLI set up on your machine

1. GitHub Repository Setup

  1. Sign in to your GitHub account and click New repository.
  2. Name the repo according to your organization’s naming convention (e.g., project-name).
  3. Add a README.md, .gitignore, and your preferred branch protection rules.
  4. Clone the repo locally:

2. Apply Organizational Best Practices

  • Establish a branching strategy (e.g., main, develop, feature branches).
  • Create issue and PR templates under .github/.
  • Configure automated workflows or GitHub Actions as needed.

3. Sample Dockerfile and Image Build

Create a Dockerfile in the project root:
Build the Docker image:

4. Local Testing of Docker Image

Run the container and verify functionality:

5. Push to GitHub

  1. Stage and commit your changes:
  2. Push to the remote:
The image shows the GitHub logo on the left and the Docker logo on the right, connected by an arrow, suggesting a workflow or integration between the two.
Avoid committing sensitive information (credentials, tokens) to the repository. Use GitHub Secrets for secure storage.
That wraps up Sprint-01. You’ve now initialized the repository, enforced best practices, built and tested your Docker image, and pushed it to GitHub. Let’s continue to Sprint-02 for CI/CD integration!

Watch Video