New to GitHub: How do I use the Projects section to manage my MERN project?

[samstudio-dev]

🏷️ Discussion Type

Question

Body

Hi everyone,

I'm new to GitHub and I'm currently working on a MERN (MongoDB, Express.js, React, Node.js) project.

I'm confused about the Projects section on GitHub. I don't understand how it's meant to be used for a software project.

I'd like to know:

• Is GitHub Projects intended for project management only, or is it also used to upload my project files?
• If anyone has a simple workflow or beginner-friendly example, I'd really appreciate it.

I've searched through the documentation, but I'm still having trouble understanding how everything fits together.

Thank you in advance for your guidance!

[TheJudge26]

GitHub Repositories: This is where your code lives. You will use Git to upload (push) your actual MERN project files, folders (src, backend, frontend, etc.), and package configuration files here.

GitHub Projects: This is strictly a project management tool (similar to Trello or Jira). You do not upload any code files here. Instead, you use it to organize your to-do lists, plan your application's features, and track your development progress using digital boards or tables.

The best way to use GitHub Projects is to link it directly to your repository so your tasks automatically update alongside your code.

watch this will help

[ahmedd761995-debug]

سوف ابحث عن اسرع حل واعود لك

[ahmedd761995-debug]

201518npx create-next-app -e https://github.com/shadcn/next-template

[hasheramin5-cyber]

From what I have learned so far, GitHub Projects is mainly for planning and tracking work rather than storing project files. I'm interested to hear how experienced developers integrate it into their daily workflow.

[RajGupta0510]

Think of GitHub Projects as a task management board, not a place to store your code.

Your project files (React, Node.js, MongoDB code, etc.) live in a GitHub repository. GitHub Projects helps you organize and track the work you're doing on that repository.

For example, if you're building a MERN app, your workflow could look like this:

• Create a repository and push your code there.
• Create a GitHub Project with columns like To Do, In Progress, and Done.
• Add tasks such as "Build Login Page," "Connect MongoDB," "Create JWT Authentication," or "Deploy Backend."
• As you work, move each task across the columns until it's completed.
• If you're using Issues, you can link them to your Project so each task is connected to your code and pull requests.

In short:

- Repository = Your source code
- Issues = Individual tasks or bugs
- Projects = A board to organize and track those tasks

When I first started, I also thought GitHub Projects was where you uploaded your project, but it's actually a project management tool that helps you plan and manage your development work.

[ahmedd761995-debug]

201518

[pira73br]

Short answer:

• Repository = where your MERN code files live (push with git)
• Projects = a task board (like Trello/Jira), NOT for uploading code

Simple beginner workflow for a MERN app:

1. Create a repository and push your code

   • frontend/ (React)
   • backend/ (Node/Express)
   • README, .gitignore, etc.

2. Create Issues for work items
   Examples:

   • Set up Express server
   • Connect MongoDB
   • Build login page
   • Add JWT auth
   • Deploy backend

3. Create a Project board
   Columns: Backlog → To Do → In Progress → Done

4. Add those Issues to the Project and move them as you work

5. Open a Pull Request for each task and link it with:
   Fixes #123

Summary:

• Repository = source code
• Issues = tasks/bugs
• Projects = board to track those tasks

If this helps, please mark as the accepted answer.

[HamiParsa]

Hi,

GitHub Projects = Project Management (NOT for code)

Code stays in Repositories

Projects are Kanban boards to track tasks (To Do → In Progress → Done)

Simple workflow:

Create a Project with 3 columns: To Do | In Progress | Done

Add tasks as cards (create Issues and link them)

Drag cards across columns as you work

That's it. Your MERN code stays in your repo – Projects just help you organize what to work on.

Hope that clears it up! 🙌

[Anupa095]

🏷️ Discussion Type

Question

Body

Hi everyone,

I'm new to GitHub and I'm currently working on a MERN (MongoDB, Express.js, React, Node.js) project.

I'm confused about the Projects section on GitHub. I don't understand how it's meant to be used for a software project.

I'd like to know:

• Is GitHub Projects intended for project management only, or is it also used to upload my project files?
• If anyone has a simple workflow or beginner-friendly example, I'd really appreciate it.

I've searched through the documentation, but I'm still having trouble understanding how everything fits together.

Thank you in advance for your guidance!

Hi,

GitHub Projects is mainly a project management tool, not a place to upload your project files.

Your Repository is where you store your source code, documentation, images, and other project files. GitHub Projects is used to organize and track the work related to that repository.

A simple workflow could be:

1. Create a Repository and push your MERN project code.
2. Create Issues for features, bugs, or tasks (e.g., "Implement login page" or "Fix authentication bug").
3. Create a GitHub Project and add those issues to it.
4. Organize the issues into columns such as To Do, In Progress, and Done.
5. As you complete tasks, move the corresponding issues across the board until they are finished.

In short:

• Repository → Stores your project files and source code.
• Issues → Track bugs, features, and tasks.
• Projects → Help you plan, organize, and monitor the progress of your work.

This is the workflow commonly used by both individual developers and software teams.

[Sultan-08]

Hi @samstudio-dev

Welcome to GitHub!

A common misunderstanding is that GitHub Projects is not where you upload or store your code. Your code belongs in a repository (repo). GitHub Projects is a project management tool that helps you plan and track your work.

For a MERN project, a typical workflow looks like this:

1. Create a repository

   • Create a new repository (for example, mern-ecommerce).
   • Push your project files to this repository using Git or GitHub Desktop.

2. Create Issues

   • Break your project into individual tasks or features.

   • Examples:

     • Set up Express server
     • Connect MongoDB
     • Build React authentication pages
     • Implement JWT authentication
     • Add shopping cart
     • Fix login bug

3. Create a Project

   • Create a new GitHub Project and choose the Board or Table layout.

   • Add columns such as:

     • Backlog
     • Todo
     • In Progress
     • Review
     • Done

4. Link Issues to the Project

   • Add your Issues as cards in the Project.
   • As you work, move them across the columns to track progress.

5. Use Pull Requests (optional)

   • If you're working with branches, create a Pull Request when a feature is complete.
   • You can link the Pull Request to the related Issue, and GitHub can automatically close the Issue when the PR is merged.

Example

Repository:

mern-todo-app

Project Board:

Backlog
 ├── Add JWT Authentication
 └── Deploy to Render

Todo
 ├── Connect MongoDB

In Progress
 ├── Design React UI

Done
 ├── Create Express API

In short:

• Repository → Stores your source code.
• Issues → Individual tasks, bugs, or feature requests.
• Projects → Organizes and tracks Issues and Pull Requests using boards or tables.
• Pull Requests → Review and merge code changes.

For a personal MERN project, you don't have to use GitHub Projects, but it's a great way to learn professional project management practices that are commonly used in software development teams.

[Mr-Nilarnab]

One feature of GitHub Projects that often gets overlooked is automation, which is what makes it much more than a simple Kanban board.

For example, a beginner-friendly MERN workflow could look like this:

1. Push your code to a Repository.

2. Create an Issue for each feature or bug (e.g., "Implement JWT authentication").

3. Add the Issue to your Project.

4. Create a branch for that Issue.

5. Open a Pull Request with a keyword like:

   Fixes #12
   

6. When the Pull Request is merged, GitHub can automatically:

   • Close the linked Issue.
   • Move the Project item to Done (if your Project is configured with workflows).

This means you spend less time manually updating your task board, and your project status stays synchronized with your code changes.

A practical MERN example might be:

• Issue: Build user authentication
• Branch: feature/user-auth
• PR: Add JWT authentication (Fixes #8)

After the PR is merged:

• Issue Allow for custom notifications for only when a discussion is answered #8 closes automatically.
• The Project item can automatically move to Done.
• Your repository history shows exactly which Pull Request completed the feature.

This is one of the reasons many teams use Repositories + Issues + Pull Requests + Projects together—they form an integrated workflow rather than four separate tools.

[SreeDharshan-GJ]

Welcome to GitHub! This is a common question when you're just getting started.

GitHub Projects is primarily a project management tool, not a place to store your source code.

A typical workflow looks like this:

Create a repository for your MERN application and push all of your project files there using Git.
Use Issues to track bugs, feature requests, or tasks (for example, "Implement user authentication" or "Fix login validation").
Create a GitHub Project (board or table view) to organize those Issues into columns such as To Do, In Progress, and Done.
Create branches for each feature or bug fix, make your changes, and open a Pull Request when you're ready to merge them back into the main branch.
As work progresses, update the associated Issue or Project item so you can easily track the status of your project.

So, in short:

Repository → Stores your code and project files.
Issues → Track tasks, bugs, and feature requests.
Projects → Organize and manage your work.
Pull Requests → Review and merge code changes.

Even if you're working alone, GitHub Projects can help you plan features and keep track of what you've completed. As your project grows or you start collaborating with others, it becomes even more useful.