Skip to content

🌴 Solutions to few of the interview coding challenges in Python 🐍

License

Notifications You must be signed in to change notification settings

adityaarakeri/Interview-solved

Repository files navigation

Build Status Contributors Issues Open Pull Requests Last Commit Stars Forks Watchers License

---

Interview solutions in Python3

There implementations are for learning purposes. If you want to contribute more efficient solutions feel free to open an issue and commit your solution.


Contributing Guidelines

To contribute make sure the Problem hasn't already added to the repo. Make sure to add the number of the Issue in your PR.

Folders and Files

  • Make sure to add the solution to the problem in the respective file folder
  • Test the solution on the respective site before submitting the solution
  • Each file must end in .py
  • Each file should be python3 compatible

Opening Issues

  • When you open an issue, please make sure the Problem is not already implemented
  • Opened Issues by existing Problem will be closed & PR made to this Issue marked as spam
  • The Contributer who opened an issue will be assigned prefered to the issue.
  • If there is no PR within about 7 Days the issue will be assigned to another Contributer.

Pull Requests

  • Only Pull Requests joined with an Issue and matching the naming-conventions
  • If there is no Issue joined in the PR your PR will be labeld as spam and closed.
  • If your PR doesn' follow the Contributing Guidelines of this Repository it will be also marked as spam and closed!

Spam Users

Users who spam this Repo with PRs/Issues that does not align the Contribution Guidelines will be blocked.

Getting Started

  • Fork this repository (Click the Form button, top right of this page)
  • Clone your fork down to your local machine
git clone git@github.com:adityaarakeri/Interview-solved.git
  • Comment to the Issue you want to work on
  • Create a branch for a new feature
git checkout -b feature/branch-name
  • Or if its a bugfix to a file
git checkout -b bugfix/branch-name
  • Make your changes (choose from the Tasks above!)
  • Commit and Push
git add .
git commit -m 'commit message'
git push origin branch-name
  • Create a New Pull Request from your forked repository ( Click the 'New Pull Request' Button located at the top of your repo)
  • Wait for your PR review and merge approval!
  • Star this repository if you had fun!

Which PR will be accepted?

  • Ones you are assigned to
  • Your PR has to link the Issue
  • Your Solution must be correct - you can check first on LeetCode (submit) if it works on different test-cases

Which PRs will be NOT accepted?

  • Ones you are NOT assigned to
  • Your PR is NOT linked to the Issue you created
  • Your Solution is not correct
  • Your PR contains more than the .py file
  • PRs that "correct" Typos or spam files with comments
  • PRs that "correct" Coding Styles - Please accept that everybody has a different style

Hacktoberfest

Every year during Hacktoberfest this Repository will be bombarded with PR's I will make sure to approve them within the time period

Run your Tests

./bin/run.sh 

Thank You!

About

🌴 Solutions to few of the interview coding challenges in Python 🐍

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages