Skip to content

Commit 94503a8

Browse files
pawangeekpawangeek
committed
Initial changes
1 parent 0eaacaf commit 94503a8

9 files changed

+371
-1
lines changed

‎.github/ISSUE_TEMPLATE/bug-report.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: 🐛 Bug Report
3+
about: If something isn't working as expected 🤔
4+
title: ''
5+
labels: bug
6+
assignees: 'pawangeek'
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Additional context**
27+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/solution-script.md

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: 🚀 Adding new solution
3+
about: I wanna add solution of a question
4+
title: ''
5+
labels: good first issue, up-for-grabs, hacktoberfest
6+
assignees: ''
7+
8+
---
9+
10+
## Leetcode Question no. -
11+
12+
**Problem name** -
13+
14+
## Instructions
15+
16+
- Create a new folder for your script and file/folder name should be appropriate.
17+
- Create a README.md in your folder for program Instructions
18+
- add requirements.txt if needed
19+
20+
### Programming Language
21+
22+
- [x] Python
23+
24+
Happy Coding

‎.github/PULL_REQUEST_TEMPLATE.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Pull Request Template
2+
3+
**Question number** -
4+
5+
### Issue no.(must) - #
6+
7+
### Self Check(Tick After Making pull Request)
8+
9+
- [ ] This issue was assigned to me.
10+
- [x] One Change in one Pull Request
11+
- [ ] My file is in proper folder (Name of folder should be Question number) (E.g. 120)
12+
- [ ] I am following clean code and Documentation and my code is well linted with flake8.
13+
- [ ] I have added README.md (With question description)
14+
- [ ] I have added sufficient comments in my code
15+
16+
**If issue was not assigned to you Please don't make a PR. It will marked as invalid.**

‎.github/workflows/codeql-analysis.yml

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
name: Flake8Linter
2+
on: [pull_request]
3+
4+
jobs:
5+
lint:
6+
runs-on: ubuntu-latest
7+
steps:
8+
- uses: actions/checkout@v2
9+
- name: Set up Python
10+
uses: actions/setup-python@v2
11+
with:
12+
python-version: '3.8'
13+
- name: Install flake8
14+
run: |
15+
python -m pip install --upgrade pip
16+
pip install flake8
17+
- name: Lint with flake8
18+
run: flake8 . --isolated --exclude=.cache,.venv,.svn,CVS,.bzr,.hg,.git,__pycache__,.tox,**/certificate_generator/**,**/migrations/** --ignore=E203,W503 --max-line-length=119

‎.github/workflows/greetings.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
name: Greetings
2+
3+
on: [pull_request_target]
4+
5+
jobs:
6+
greeting:
7+
runs-on: ubuntu-latest
8+
steps:
9+
- uses: actions/first-interaction@v1
10+
with:
11+
repo-token: "${{ secrets.GITHUB_TOKEN }}"
12+
pr-message: 'Congratulations!! 🎉 @${{ github.actor }} for making your first PR. We will review the changes soon and merge finally.😊 Do give a star ⭐ meanwhile if you like this project. '

‎.gitignore

+68
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
2+
# Byte-compiled / optimized / DLL files
3+
__pycache__/
4+
*.pyc
5+
*.pyo
6+
*.pyd
7+
*.local
8+
9+
# C extensions
10+
*.so
11+
12+
# Distribution / packaging
13+
.Python
14+
env/
15+
build/
16+
develop-eggs/
17+
dist/
18+
downloads/
19+
eggs/
20+
.eggs/
21+
lib/
22+
lib64/
23+
parts/
24+
sdist/
25+
var/
26+
*.egg-info/
27+
.installed.cfg
28+
*.egg
29+
30+
# PyInstaller
31+
# Usually these files are written by a python script from a template
32+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
33+
*.manifest
34+
*.spec
35+
36+
# Installer logs
37+
pip-log.txt
38+
pip-delete-this-directory.txt
39+
40+
# Unit test / coverage reports
41+
htmlcov/
42+
.tox/
43+
.coverage
44+
.coverage.*
45+
.cache/
46+
.hypothesis/
47+
coverage.xml
48+
49+
# IPython Notebook
50+
.ipynb_checkpoints
51+
52+
# pyenv
53+
.python-version
54+
55+
# virtualenv
56+
venv/
57+
.venv/
58+
ENV/
59+
60+
# pytest
61+
.pytest_cache/
62+
63+
# IDE
64+
.idea/
65+
.vscode/
66+
67+
# macOS
68+
.DS_Store

‎CODE_OF_CONDUCT.md

+76
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [email protected]. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎CONTRIBUTING.md

+77
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
# Contributing Guidelines
2+
3+
This documentation contains a set of guidelines to help you during the contribution process.
4+
We are happy to welcome all the contributions from anyone willing to improve/add new scripts to this project. Thank you for helping out and remember,
5+
**no contribution is too small.**
6+
7+
# Submitting Contributions👩‍💻👨‍💻
8+
Below you will find the process and workflow used to review and merge your changes.
9+
## Step 1 : Find an issue
10+
- Take a look at the Existing Issues or create your **own** Issues!
11+
- Wait for the Issue to be assigned to you after which you can start working on it.
12+
- Note : Every change in this project should/must have an associated issue.
13+
14+
15+
## Step 2 : Fork the Project
16+
- Fork this Repository. This will create a Local Copy of this Repository on your Github Profile. Keep a reference to the original project in `upstream` remote.
17+
```
18+
$ git clone https://github.com/<your-username>/Leetcode-scripts
19+
$ cd Automation-scripts
20+
$ git remote add upstream https://github.com/python-geeks/Leetcode-scripts
21+
```
22+
23+
![Inkedfork_LI](https://user-images.githubusercontent.com/42181691/135037282-28d32b80-0e20-456c-b6d0-d21e50bd8a26.jpg)
24+
25+
26+
- If you have already forked the project, update your copy before working.
27+
```
28+
$ git remote update
29+
$ git checkout <branch-name>
30+
$ git rebase upstream/<branch-name>
31+
```
32+
## Step 3 : Branch
33+
Create a new branch. Use its name to identify the issue your addressing.
34+
```
35+
# It will create a new branch with name Branch_Name and switch to that branch
36+
$ git checkout -b branch_name
37+
```
38+
## Step 4 : Work on the issue assigned
39+
- Work on the issue(s) assigned to you.
40+
- Add all the files/folders needed.
41+
- After you've made changes or made your contribution to the project add changes to the branch you've just created by:
42+
```
43+
# To add all new files to branch Branch_Name
44+
$ git add .
45+
```
46+
## Step 5 : Commit
47+
- To commit give a descriptive message for the convenience of reveiwer by:
48+
```
49+
# This message get associated with all files you have changed
50+
$ git commit -m "message"
51+
```
52+
- **NOTE**: A PR should have only one commit. Multiple commits should be squashed.
53+
## Step 6 : Work Remotely
54+
- Now you are ready to your work to the remote repository.
55+
- When your work is ready and complies with the project conventions, upload your changes to your fork:
56+
57+
```
58+
# To push your work to your remote repository
59+
$ git push -u origin Branch_Name
60+
```
61+
62+
## Step 7 : Pull Request
63+
- Go to your repository in browser and click on compare and pull requests. Then add a title and description to your pull request that explains your contribution.
64+
65+
- Voila! Your Pull Request has been submitted and will be reviewed by the moderators and merged.🥳
66+
67+
## Need more help?🤔
68+
You can refer to the following articles on basics of Git and Github and also contact the Project Mentors, in case you are stuck:
69+
- [Forking a Repo](https://help.github.com/en/github/getting-started-with-github/fork-a-repo)
70+
- [Cloning a Repo](https://help.github.com/en/desktop/contributing-to-projects/creating-an-issue-or-pull-request)
71+
- [How to create a Pull Request](https://opensource.com/article/19/7/create-pull-request-github)
72+
- [Getting started with Git and GitHub](https://towardsdatascience.com/getting-started-with-git-and-github-6fcd0f2d4ac6)
73+
- [Learn GitHub from Scratch](https://lab.github.com/githubtraining/introduction-to-github)
74+
75+
76+
## Tip from us😇
77+
It always takes time to understand and learn. So, do not worry at all. We know **you have got this**!💪

‎README.md

+53-1
Original file line numberDiff line numberDiff line change
@@ -1 +1,53 @@
1-
# Leetcode-scripts
1+
<h1 align=center> Leetcode-scriptss </h1>
2+
3+
**Do you know any solution that can help a Panda to be more smarter or to be a coder xD (Only supporting Python solution**
4+
5+
<p align="center">
6+
<a href="#"><img src="https://forthebadge.com/images/badges/built-with-love.svg" /></a>&nbsp;&nbsp;
7+
<a href="#"><img src="https://forthebadge.com/images/badges/made-with-python.svg" /></a>&nbsp;&nbsp;
8+
<a href="#"><img src="https://forthebadge.com/images/badges/built-by-developers.svg" /></a>&nbsp;&nbsp;
9+
</p>
10+
11+
## Here are the steps to Make contribute 👣
12+
- [x] Take a look at [Contributing Guide](https://github.com/python-geeks/Leetcode-scripts/blob/main/CONTRIBUTING.md) (Necessary)
13+
- [x] Create an issue for making any change to code. when issue will be approve you can make a change.
14+
- [x] Pull latest change from upstream branch before starting the changing code.
15+
- [x] Add your file in proper folder(Question number) with README.md in it. Add requirements.txt if needed.
16+
- [x] Please use flake8 linting in your code (See below to check flake8 linting)
17+
18+
<h1 align="center"> 🎃 HacktoberFest-2021 🎃</h1>
19+
20+
![Opensource](https://img.shields.io/badge/openSource-%E2%9D%A4-blue) ![PR](https://img.shields.io/badge/PRs-welcome-green) ![hacktoberfest](https://img.shields.io/badge/Hacktoberfest-2021-red) ![friendly](https://img.shields.io/badge/beginner-friendly-l)
21+
22+
# What is HacktoberFest?
23+
24+
Hacktoberfest is a month long event where people are awarded for contributing to open source projects 🙌, and we're joining the party .Hosted by DigitalOcean for the 8th year in a row, Hacktoberfest encourages participation in giving back to the open source community by completing pull requests, participating in events, and donating to open source projects.
25+
26+
# More details
27+
28+
Hacktoberfest is open to everyone in our global community. Whether you’re a seasoned contributor or looking for projects to contribute to for the first time, you’re welcome to participate.
29+
30+
Pull requests can be made in any participating GitHub or GitLab hosted repository/project. Look for the 'hacktoberfest' topic to know if a repository/project is participating in Hacktoberfest. Pull requests must be approved by a maintainer of the repository/project to count.
31+
32+
You can sign up anytime between October 1 and October 31. Just be sure to sign up on the official Hacktoberfest website for your pull requests to count.
33+
34+
# Rules for participation
35+
36+
* Pull requests can be submitted to any opted-in repository on GitHub or GitLab.
37+
* The pull request must contain commits you made yourself.
38+
* If a maintainer reports your pull request as spam, it will not be counted toward your participation in Hacktoberfest.
39+
* If a maintainer reports behavior that’s not in line with the project’s code of conduct, you will be ineligible to participate.
40+
* To get a shirt, you must make four approved pull requests (PRs) on opted-in projects between October 1-31 in any time zone.
41+
* This year, the first 55,000 participants can earn a T-shirt.
42+
43+
# Quality Guidelines
44+
45+
* Pull requests that are automated e.g. scripted opening pull requests to remove whitespace / fix typos / optimize images.
46+
* Pull requests that are disruptive e.g. taking someone else's branch/commits and making a pull request.
47+
* Pull requests that are regarded by a project maintainer as a hindrance vs. helping.
48+
* Something that's clearly an attempt to simply +1 your pull request count for October.
49+
* Last but not least, one pull request to fix a typo is fine, but 5 pull requests to remove a stray whitespace is not.
50+
51+
### Note
52+
53+
**A pull request is considered approved once it has an overall approving review from maintainers, or has been merged by maintainers, or has been given the 'hacktoberfest-accepted' label. A pull request with any label containing the word 'spam' or 'invalid' will be considered ineligible for Hacktoberfest.**

0 commit comments

Comments
 (0)