algorithms icon indicating copy to clipboard operation
algorithms copied to clipboard

Organize directories: Move submissions into their respective domain folders

Open Copilot opened this issue 6 months ago • 1 comments

This PR reorganizes the repository structure to follow the guidelines specified in CONTRIBUTING.md. The expected structure is:

├── problem category (or sub-category)
│   ├── programming language
│   │   └── your code!

Changes Made

1. Moved files from domain root directories to language subdirectories

Previously, many files were directly in domain folders without proper language organization:

  • graphs/Dijkstra.cppgraphs/cpp/Dijkstra.cpp
  • greedy_algorithms/*.cppgreedy_algorithms/cpp/
  • misc/mod_inverse_euclidean_algorithm.cmisc/c/
  • misc/random_file_name_gen.pymisc/python/
  • networking/mail_sender.pynetworking/python/
  • sorting/TimSort.javasorting/java/
  • sorting/Toplogical sort.cppsorting/cpp/
  • system_programming/grammar_left_factoring.cppsystem_programming/cpp/
  • tictactoe_game/tictactoe.pytictactoe_game/python/
  • dynamic_control/PID_algo_with_documentation.cdynamic_control/c/

2. Resolved case conflict directories

The repository had several directories with "(Case Conflict)" suffixes that needed to be merged:

  • Merged Gnome_sort (Case Conflict) into Gnome_sort
  • Merged Heap_sort (Case Conflict) into Heap_sort
  • Merged Selection_sort (Case Conflict) into Selection_sort

All files from these conflicting directories were properly organized into their respective language subdirectories.

Results

  • 337 code files are now properly organized according to the contributing guidelines
  • All files now follow the expected 3-level directory structure: domain/language/code
  • No files remain at incorrect depth levels
  • All case conflicts have been resolved
  • Repository structure is now consistent and maintainable

This organization will make it easier for contributors to find the right location for their submissions and maintain consistency across the repository.

Fixes #67.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot avatar Sep 01 '25 06:09 Copilot

@felipecustodio 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.

Copilot avatar Sep 01 '25 06:09 Copilot