├── README.md ├── questions └── README.md ├── solutions └── README.md ├── testcases └── README.md └── workflow.md /README.md: -------------------------------------------------------------------------------- 1 | Competitive Programming Repository 2 | ---------------------------------- 3 | 4 | *Welcome!* This repository is all about the various competitive programming questions we will be attempting as part of the CodeChef Chapter at Model Engineering College Thrikkakara. 5 | 6 | Questions we expect you to solve will be updated here and you will be informed about the same as and when it happens. 7 | 8 | Your submissions for the programming challenges can be added to this repository. Please make sure you have read the workflow document before submitting. 9 | 10 | ### Getting Started 11 | ********************* 12 | To get started using this repository, make sure you have ```git``` installed. If not kindly go through the [installation instructions](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). 13 | 14 | If you're unfamiliar with git commands, we suggest you try out forking on a demo repository before forking this repository. 15 | 16 | Instructions on how to fork and clone a repository can be found [here](https://help.github.com/en/articles/fork-a-repo) 17 | 18 | Once you've got a working copy of the repository on your system, make sure you work on your solutions in a new branch and keep your master branch clean of any changes from the main repository. [Instructions for branching](https://confluence.atlassian.com/bitbucket/branching-a-repository-223217999.html) (Follow the instructions for branching your repository locally). 19 | 20 | 21 | Delete your branch once the pull request has been merged. always make sure your master branch is [in sync with the upstream](https://help.github.com/en/articles/syncing-a-fork) -------------------------------------------------------------------------------- /questions/README.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/codechef-mec/Competitive-Programming/f4acfe3ed042e740a586872dbb2abab5c8f04226/questions/README.md -------------------------------------------------------------------------------- /solutions/README.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/codechef-mec/Competitive-Programming/f4acfe3ed042e740a586872dbb2abab5c8f04226/solutions/README.md -------------------------------------------------------------------------------- /testcases/README.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/codechef-mec/Competitive-Programming/f4acfe3ed042e740a586872dbb2abab5c8f04226/testcases/README.md -------------------------------------------------------------------------------- /workflow.md: -------------------------------------------------------------------------------- 1 | Workflow Document 2 | ------------------ 3 | 4 | This document contains instructions on how to submit your solutions/changes to the repository. 5 | 6 | ### Submitting a solution 7 | 8 | Initial Steps : 9 | 10 | - Create a new branch in your forked repository 11 | - Create a new folder under the directory `solutions` with your GitHub username as the folder name 12 | - Create a README.md file inside this folder with basic information about yourself. 13 | - Submit a Pull Request for us to merge this branch with our master. 14 | - Once the pull request has been merged, you can delete this branch from your fork and sync your master. 15 | 16 | Submitting : 17 | 18 | - Create a new branch for each solution you wish to submit. 19 | - Once you feel you've reached a solution, add it to a folder in the same structure as the `questions` folder. 20 | - This file should be in the same subdirectory as the question for which this file is intended (in the questions directory) and the filename should be `.py` or whatever extension, based on your preferred programming language. 21 | - Submit a pull request with the following details : 22 | - github username : 23 | - full name : 24 | - class : 25 | - details regarding pull request (question number, solution language, whether full solution or partial etc.) 26 | - additional comments : 27 | - Notify one of the admins if the pull request has not been merged even after a week. 28 | - Once the Pull Request has been merged, you can delete this branch and start a new branch for attempting the next question. 29 | 30 | ###### Note : You can have multiple branches for attempting multiple questions simultaneously, but make sure no conflicts occur when submitting the PRs. 31 | 32 | ### Suggesting a change 33 | 34 | If you feel you can improve this repository or contribute to it in any way (even a simple change in documentation), follow the steps detailed below : 35 | 36 | - Create an Issue detailing the change intended and how you plan to proceed with making the changes. 37 | - If we feel the change is necessary, we will assign you the issue and you can start working on it in the same workflow above *(branch, PR, delete branch)* 38 | - The PR should contain the following line at the top : 39 | ``` Fixes #XXX``` where ```XXX``` references the issue that you raised earlier. Also, detail what all changes have been made and possible shortcomings (if any) of the commits. --------------------------------------------------------------------------------