[](https://github.com/MakeContributions/DSA/actions/workflows/dotnet.yml) [](https://github.com/MakeContributions/DSA/actions/workflows/cpp.yml) [](https://github.com/MakeContributions/DSA/actions/workflows/go.yml) [](https://github.com/MakeContributions/DSA/actions/workflows/node.js.yml) [](https://github.com/MakeContributions/DSA/actions/workflows/python.yml) [](https://github.com/MakeContributions/DSA/actions/workflows/codespell.yml) [](https://github.com/MakeContributions/DSA/actions/workflows/codeql-analysis.yml) [](https://discord.gg/ydWxdqbTyK) # Data Structures and Algorithm Data structure and Algorithm (DSA) ## Explanations - [English](./docs/en) - [Español](./docs/es) - [Português](./docs/pt) - [Turkish](./docs/tr) - [繁體中文](./docs/zh-tw) - [日本語](./docs/ja) ## Contribution Guidelines ### 1. Contribution Specifications The problem being contributed must either be a simple **file** (**Eg.** [`kruskal-algorithm.cpp`](./algorithms/CPlusPlus/Graphs/kruskal-algorithm.cpp), [`linear-search.java`](./algorithms/Java/searching/linear-search.java)) or a more complex **directory** ([`palindrome/`](./algorithms/Rust/strings/palindrome)). This is a unit `problem`. The directory tree has the following convention of `algorithms/{language}/{category}/{problem}`, where `{language}` represents the language code of the problem (**Eg.** `CPlusPlus` for C++, `CSharp` for C# etc.), `{category}` is the topic or category of the problem being contributed (**Eg.** `strings`, `sorting`, `linked-lists` etc.), and `{problem}` is a conforming name to the problem (**Eg.** `linear-search.cpp`, `palindrome`, `queue-linked-list.cpp` etc.) A unit `problem` must conform to the following specifications: - The name should be in lowercase. (**Eg.** `palindrome/`, `binary-search.cpp` etc.). - Each word must be separated by a **dash** or a **hyphen** (`-`). **If you have a problem that belongs to a new _topic_ or _category_ than one which are present:** 1. Create a new folder and an index for it inside (a readme, `README.md` file). 2. To each new index file, write the readme with your `problem` in it ([Markdown Documentation](https://guides.github.com/features/mastering-markdown/)). 3. The folder name can also only contain **lowercase characters** and **dashes** or **hyphens** (`-`) (Eg. `strings` `sorting` etc.) #### Simple (File) Contributions The file should conform to the `problem` specification, and the extension (**Eg.** `linear-search.java`, `kruskal-algorithm.cpp`, `count-inversions.js` etc.) #### Project/Folder-based Contributions The project and folder-based contributions have a bit more stricter contribution specifications. The folder should conform to the `problem` specification, along with the following specifications **Folder Structure** ```bash problem-name\ | - .gitignore | - README.md | - Makefile # or the specific specification/requirements/configuration file | - src\ | - main.ext ``` #### `README.md` Specification / Template ````markdown #