---
title: "Discussion on \"Deep Dive into GitHub Issues: Tracking and Managing Project Progress\" | Hashnode"
description: "Discussion on \"Deep Dive into GitHub Issues: Tracking and Managing Project Progress\". Learn to use GitHub Issues for tracking and managing project progress, including creating, linking, and closing issues effectively"
url: "https://hashnode.com/posts/deep-dive-into-github-issues-tracking-and-managing-project-progress/66813679244d52c5af089966"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Deep Dive into GitHub Issues: Tracking and Managing Project Progress](https://githubjourney.hashnode.dev/deep-dive-into-github-issues-tracking-and-managing-project-progress?utm_source=hashnode&utm_medium=feed)

Learn to use GitHub Issues for tracking and managing project progress, including creating, linking, and closing issues effectively

Jun 30, 2024 · 5 min read · githubjourney.hashnode.dev  
Updated Jul 1, 2024  
Read the article

-   [#github](https://hashnode.com/tag/github)
-   [#github-issues](https://hashnode.com/tag/github-issues)

## Written by

[Aseru Kevin Ziyada](https://hashnode.com/@AseruKevinZiyada)

@AseruKevinZiyada · Kampala, Uganda

  
[View profile](https://hashnode.com/@AseruKevinZiyada)

A dev

Kevin Ziyada Aseru is a Software Developer, AI/ML Engineer, and UI/UX Designer based in Kampala, Uganda. She serves as the technical lead and mentor at the Research Code Academy, driving technical excellence across pan-African developer cohorts. As a co-founder of the innovation studio Research Code Respond (RCR), Kevin builds community-centered digital frameworks that merge advanced data engineering with ethical technology solutions to solve regional societal challenges

## Responses 1

Markdown supported · ⌘↵ to post

[Ayiko Andrew](https://hashnode.com/@Ayikoandrew)

[Jun 30, 2024](https://hashnode.com/posts/deep-dive-into-github-issues-tracking-and-managing-project-progress/66813679244d52c5af089966/comment/66813c6a9925e9f80e926a33)

Am alittle bit confused when you are pushing changes to github I have always thought it is like so git push origin main but today I am seeing a git push fix/... Help me here. Btw great article. It is really helpful.

[Aseru Kevin Ziyada](https://hashnode.com/@AseruKevinZiyada)

[Jul 1, 2024](https://hashnode.com/posts/deep-dive-into-github-issues-tracking-and-managing-project-progress/66813679244d52c5af089966/comment/66813c6a9925e9f80e926a33#reply-66824116286c49bb80c882c0)

Thank you for the kind words! I'm glad you found the article helpful.

About the question:

When you push changes to GitHub, you're uploading your changes from your local branch to a branch on the remote repository. The command `git push origin main` pushes your changes to the `main` branch on the remote repository.

However, if you're working on a new feature or fixing a bug, it's a good practice to create a separate branch for your changes. For example, I created a branch called `fix/division-by-zero-handling`. To push changes to this branch, I used

```
git push origin fix/division-by-zero-handling
```

This command pushes changes to a branch named `fix/division-by-zero-handling` on the remote repository, keeping your work organized and making it easier to manage different features or bug fixes. Once your work is reviewed and approved, it can be merged into the `main` branch. Hope you have now understood it

[Ayiko Andrew](https://hashnode.com/@Ayikoandrew)

[Jul 1, 2024](https://hashnode.com/posts/deep-dive-into-github-issues-tracking-and-managing-project-progress/66813679244d52c5af089966/comment/66813c6a9925e9f80e926a33#reply-668247bbfd5cc947b5778158)

Thank you. I have.

[Aseru Kevin Ziyada](https://hashnode.com/@AseruKevinZiyada)

[Jul 1, 2024](https://hashnode.com/posts/deep-dive-into-github-issues-tracking-and-managing-project-progress/66813679244d52c5af089966/comment/66813c6a9925e9f80e926a33#reply-66829c82e288586ceb80b8a8)

That's great