Redirect to Root after File Upload to Subfolder

[dahoum]

Select Topic Area

Question

Body

Why does the GitHub web interface redirects to / after I upload a file to a subfolder?

Isn't it more logical to stay in this subfolder?

I might have other things to do there.

Now every time I have navigate back from / to the subfolder after file upload.

[Nikhil9211]

GitHub’s web interface currently redirects you back to the repository root (/) after uploading a file, even if you were inside a subfolder. This is simply how the UI is designed—it treats uploads as repository‑level actions rather than folder‑specific ones.
While it works consistently, it can feel inconvenient because you often want to stay in the same subfolder to continue working. Unfortunately, GitHub doesn’t preserve folder context after an upload.
Workarounds:
• Navigate into the subfolder first and use drag‑and‑drop to upload files—this usually keeps you in the folder view.
• Upload multiple files at once to reduce the number of redirects.
• For structured projects, it’s more efficient to use Git locally (git add, git commit, git push) so you can place files directly into the right subfolders without dealing with the redirect.
In short, the redirect is a limitation of the current GitHub web UI, not a bug. If you’re working heavily with subfolders, using Git locally is the most practical solution.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[Hasith-Dissanayake]

This is a confirmed limitation of the GitHub web UI — it's not a bug, but it is a genuine UX pain point that many people have run into.
Why it happens: After committing a file upload, GitHub redirects you to the repository root to reflect the new commit state. The UI treats the upload as a repository-level action rather than staying folder-aware.

Workarounds (best to least practical)

1. Drag and drop directly onto the subfolder view
   Navigate into your subfolder first, then drag files onto the file listing area (not the "Add file" button). This tends to keep you in the folder context after the upload completes — though it's not 100% consistent.
2. Upload multiple files at once
   If you have several files to add to the same subfolder, upload them all in one commit instead of one by one. This reduces how often you hit the redirect.
3. Use Git locally for repeated subfolder work
   For any workflow where you're regularly adding files to a specific subfolder, a local Git setup is far more efficient:
   bashgit add path/to/your/subfolder/
   git commit -m "Add files to subfolder"
   git push
   You stay exactly where you are, and there's no redirect at all.
4. Use GitHub CLI (gh)
   bashgh repo clone your-repo

add files, then:

git add subfolder/ && git commit -m "..." && git push

Feature request
If this bothers you, it's worth upvoting or creating a dedicated feature request in the Repositories category here with the specific ask: "After uploading a file to a subfolder, redirect back to that subfolder instead of the repository root." That's a well-scoped, reasonable UX improvement that GitHub could realistically implement.

TL;DR — It's a current UI limitation with no perfect fix, but drag-and-drop onto the subfolder view is the closest workaround. For repeated subfolder work, local Git is the practical answer.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬