Demo Commit changes to github repo

Welcome back. In the previous lesson we verified the application runs locally. Now we’ll stage, commit, and push the code to a GitHub repository, then open and merge a pull request (PR). You can perform these steps from VS Code’s UI or the integrated terminal; below are the terminal commands that correspond to the UI actions.

1) Stage and commit your changes

Add the files you want to include in the commit. You can list specific files or use . to add everything in the working directory:

git add app.py Dockerfile README.md requirements.txt
# or
git add .

git commit -m "Python application"

2) Verify your current branch

Check which branch you are on before pushing changes:

git branch
# Example output:
# * main

If you need to work on a feature branch (recommended), create it, switch to it, and push it to the remote:

git checkout -b sprint-01-ABC-123
git push -u origin sprint-01-ABC-123

Use a branch name that matches your team’s convention. Including a Jira ticket or task ID (like ABC-123) is common and helps trace the change back to the requirement.

3) Dockerfile used in this project

This repository uses a minimal Flask-based Docker image:

FROM python:3.8-slim-buster

WORKDIR /app

COPY requirements.txt requirements.txt
RUN pip3 install --no-cache-dir -r requirements.txt

COPY . .

ENV FLASK_APP=app.py
ENV FLASK_RUN_HOST=0.0.0.0

CMD ["flask", "run"]

This Dockerfile sets up a lightweight Python 3.8 image, installs dependencies from requirements.txt, copies the project files, and starts Flask listening on all interfaces.

4) Create a pull request on GitHub

After pushing your branch, open the repository on GitHub and refresh the page. GitHub typically shows a prompt to open a pull request for the recently pushed branch. Click “Compare & pull request” (or a similar button), add a descriptive title and summary, assign reviewers, and submit the PR. When ready, reviewers approve and the PR can be merged into main. In this lesson we merge our PR ourselves.

A GitHub pull request page for the repository "learnwithraghu/github-example" titled "Python application #1." It shows an open PR with comments, status checks indicating no conflicts, and a green "Merge pull request" button.

5) Verify merged changes on the main branch

Once the PR is merged, open the repository main branch to confirm all files are present and your changes are visible in the file list and commit history.

A screenshot of a GitHub repository page (learnwithraghu/github-example) showing the main branch file list — Dockerfile, README.md, app.py, and requirements.txt. The README preview at the bottom is titled "Docker flask application."

With the merge complete, the sprint task is finished from a code-delivery perspective.

Quick reference: common Git commands

Action	Command	Notes
Stage specific files	`git add app.py Dockerfile README.md requirements.txt`	Add only listed files
Stage everything	`git add .`	Stages all modified/new files
Commit	`git commit -m "Your commit message"`	Use clear, descriptive messages
Create & switch to branch	`git checkout -b sprint-01-ABC-123`	Follow branch naming conventions
Push branch & set upstream	`git push -u origin sprint-01-ABC-123`	Use `-u` to set default upstream
Check branches	`git branch`	Current branch is marked with `*`

Typical pull request workflow

Push a feature branch to the remote.
Open a PR and add a descriptive title and summary.
Add reviewers and wait for feedback and approvals.
Address comments (if any) with additional commits.
Merge the PR after approvals and successful CI checks.
Pull main locally to sync your environment: git checkout main && git pull origin main.

Links and references

That is it for this lesson. See you in the next lesson.

Introduction

Sprint-02

Sprint-03

Sprint-04

Sprint-05

Sprint-06

Sprint-07

Conclusion

Sprint-01

Demo Commit changes to github repo

1) Stage and commit your changes

2) Verify your current branch

3) Dockerfile used in this project

4) Create a pull request on GitHub

5) Verify merged changes on the main branch

Quick reference: common Git commands

Typical pull request workflow

Links and references

Watch Video

​1) Stage and commit your changes

​2) Verify your current branch

​3) Dockerfile used in this project

​4) Create a pull request on GitHub

​5) Verify merged changes on the main branch

​Quick reference: common Git commands

​Typical pull request workflow

​Links and references

Watch Video

1) Stage and commit your changes

2) Verify your current branch

3) Dockerfile used in this project

4) Create a pull request on GitHub

5) Verify merged changes on the main branch

Quick reference: common Git commands

Typical pull request workflow

Links and references