// the find
KrishnaBysani/AUTOMOBILE-PARTS-INVENTORY-MANAGEMENT-SYSTEM
System using C programming Language to manage automobile parts in all the warehouse
A university C assignment implementing a text-file-backed inventory tracker for a fictional auto-parts warehouse scenario, covering CRUD on parts, supplier records, low-stock reporting, and basic search. It's coursework (the repo even embeds the assignment brief and a student ID in the folder name), not a tool anyone would install.
The scope matches a real systems-programming exercise reasonably well: file I/O for persistence, sorting by part id, a low-stock threshold report, and a one-supplier-to-many-parts relationship modeled across separate text files. There's a flowchart and pseudocode doc alongside the code, which is more design documentation than most student submissions bother with.
The repo ships compiled build artifacts (x64/Debug .exe, .obj, .pdb, .ilk, .tlog files) committed straight into source control, which a .gitignore exists but clearly isn't doing its job on. The source itself is duplicated and ambiguous — there's both a root-level main.c and a nested 'Final assignment.c' inside a differently-named folder, with no README pointer to which one is canonical or how to build it. Zero stars, zero forks, last pushed in 2023, and the description is literally the assignment prompt restated — this is a homework submission, not a maintained project, and the data files (war.txt, wbz.txt, wsl.txt) suggest flat-file 'parsing' with no error handling visible from the structure, which is the usual failure point in this style of exercise.