├── .github
├── ISSUE_TEMPLATE
│ ├── bug.md
│ ├── documentation.md
│ ├── features.md
│ ├── proposal.md
│ └── question.md
├── pull_request_template.md
├── reviewer_config.yml
└── workflows
│ ├── auto-assign.yml
│ ├── auto-reviewer.yml
│ └── greetings.yml
├── .gitignore
├── CODE_OF_CONDUCT.md
├── Dockerfile
├── LICENSE
├── README.md
├── action.yml
├── img
├── White and Green Gaming Badge Logo.png
└── sample.jpeg
├── requirements.txt
└── src
└── main.py
/.github/ISSUE_TEMPLATE/bug.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: 🐛 Bug Report
3 | about: Submit a bug report to help us improve
4 | labels: "bug"
5 | ---
6 |
7 | ## 🐛 Bug Report
8 |
9 | (A clear and concise description of what the bug is.)
10 |
11 | ### Have you read the [Contributing Guidelines on Pull Requests]()?
12 |
13 | (Write your answer here.)
14 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/documentation.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: 📚 Documentation
3 | about: Report an issue related to documentation
4 | labels: "documentation"
5 | ---
6 |
7 | ## 📚 Documentation
8 |
9 | (A clear and concise description of what the issue is.)
10 |
11 | ### Have you read the [Contributing Guidelines on Pull Requests]()?
12 |
13 | (Write your answer here.)
14 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/features.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: 🚀 Feature
3 | about: Submit a proposal for a new feature
4 | labels: "feature"
5 | ---
6 |
7 | ## 🚀 Feature
8 |
9 | (A clear and concise description of what the feature is.)
10 |
11 | ### Have you read the [Contributing Guidelines on Pull Requests](https://github.com/TesseractCoding/NeoAlgo/blob/master/CONTRIBUTING.md#reporting-new-issues)?
12 |
13 | (Write your answer here.)
14 |
15 | ## Motivation
16 |
17 | (Please outline the motivation for the proposal.)
18 |
19 | ## Pitch
20 |
21 | (Please explain why this feature should be implemented and how it would be used.)
22 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/proposal.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: 💥 Proposal
3 | about: Propose a non-trivial change to Issue_Watcher
4 | labels: "proposal"
5 | ---
6 |
7 | ## 💥 Proposal
8 |
9 | (A clear and concise description of what the proposal is.)
10 |
11 | ### Have you read the [Contributing Guidelines on Pull Requests](https://github.com/TesseractCoding/NeoAlgo/blob/master/CONTRIBUTING.md#reporting-new-issues)?
12 |
13 | (Write your answer here.)
14 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/question.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: ❓ Questions and Help
3 | about: If you have questions, please check the below links
4 | labels: "question"
5 | ---
6 |
7 | ## ❓ Questions and Help
8 |
9 | ### Please note that this issue tracker is not a help form and this issue will be closed.
10 |
11 | Please contact us instead.
12 |
13 | - [Website](https://www.tesseractcoding.tech/)
14 | - [Email](team@tesseractcoding.tech)
15 | - [GitHub](https://github.com/TesseractCoding)
16 | - [Instagram](https://www.instagram.com/tesseractcoding/)
17 | - [LinkedIn](https://www.linkedin.com/company/tesseract-coding/)
18 | - [Medium](https://medium.com/tesseract-coding)
19 | - [Telegram](https://t.me/tesseractcoding)
20 | - [YouTube](https://www.youtube.com/c/TesseractCoding/)
21 |
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 |
10 |
11 | ### Have you read the [Contributing Guidelines on Pull Requests]()?
12 |
13 | (Write your answer here.)
14 |
15 | ### Description
16 |
17 | (Write your answer here.)
18 |
19 | ### Checklist
20 |
21 | - [ ] I've read the contribution guidelines.
22 | - [ ] I've checked the issue list before deciding what to submit.
23 | - [ ] I've edited the `README.md` and link to my code.
24 |
25 | ## Related Issues or Pull Requests
26 |
27 | (Write your answer here.)
28 |
--------------------------------------------------------------------------------
/.github/reviewer_config.yml:
--------------------------------------------------------------------------------
1 | # Set to true to add reviewers to pull requests
2 | addReviewers: true
3 |
4 | # Set to true to add assignees to pull requests
5 | addAssignees: false
6 |
7 | # A list of reviewers to be added to pull requests (GitHub user name)
8 | reviewers:
9 | - anushkrishnav
10 | - HarshCasper
11 | - iamrajiv
12 | - atarax665
--------------------------------------------------------------------------------
/.github/workflows/auto-assign.yml:
--------------------------------------------------------------------------------
1 | name: Assign
2 |
3 | on:
4 | schedule:
5 | - cron: '*/2 * * * *'
6 | issue_comment:
7 | types: [created]
8 |
9 | jobs:
10 | slash_assign:
11 | # If the acton was triggered by a new comment that starts with `/assign`
12 | # or a on a schedule
13 | if: >
14 | (github.event_name == 'issue_comment' && startsWith(github.event.comment.body, '/assign')) ||
15 | github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'
16 | runs-on: ubuntu-latest
17 | steps:
18 | - name: Assign the user or unassign stale assignments
19 | uses: JasonEtco/slash-assign-action@v0.0.3
20 | with:
21 | assigned_label: Assigned
22 | days_until_warning: 7
23 | days_until_unassign: 14
24 | stale_assignment_label: Open
25 |
--------------------------------------------------------------------------------
/.github/workflows/auto-reviewer.yml:
--------------------------------------------------------------------------------
1 | name: 'Auto Assign Reviewers to Pull Requests'
2 | on:
3 | pull_request:
4 | types: [opened, reopened]
5 | jobs:
6 | add-reviews:
7 | runs-on: ubuntu-latest
8 | steps:
9 | - uses: kentaro-m/auto-assign-action@v1.1.2
10 | with:
11 | repo-token: "${{ secrets.GITHUB_TOKEN }}"
12 | configuration-path: .github/reviewer_config.yml
13 |
--------------------------------------------------------------------------------
/.github/workflows/greetings.yml:
--------------------------------------------------------------------------------
1 | name: Greetings
2 |
3 | on:
4 | issues:
5 | types: [opened]
6 | pull_request:
7 | types: [opened]
8 |
9 | jobs:
10 | greeting:
11 | runs-on: ubuntu-latest
12 | steps:
13 | - uses: Karthik-Nayak98/Greeting-action@main
14 | with:
15 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
16 | issue_message: 'Hello @${{github.actor}},
17 | Thank you for opening an issue. :partying_face:
18 | To get assigned to this particular issue please use /assign
19 | Check this guide before contributing.'
20 | PR_message:
21 | ' :partying_face: Congratulations :tada:
:pray:
22 | Thank you @${{github.actor}} for taking out your time and contributing to our project. Our team will now review this and if everything looks good it will be merged.'
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | *.env
2 |
3 | *.dist
4 | *.vscode/
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
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 team@tesseractcoding.tech. 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
77 |
--------------------------------------------------------------------------------
/Dockerfile:
--------------------------------------------------------------------------------
1 |
2 | # action will be run in python3 container
3 | FROM python:3
4 | # copying requirements.txt and install the action dependencies
5 | COPY requirements.txt /requirements.txt
6 | RUN pip install -r /requirements.txt
7 | # main.py is the file that will contain the codes that we want to run for this action.
8 | COPY src/main.py /src/main.py
9 | # we will just run our main.py as our docker entrypoint by python main.py
10 | CMD ["python", "/src/main.py"]
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 |
2 | The MIT License (MIT)
3 |
4 | Copyright (c) 2018 GitHub, Inc. and contributors
5 |
6 | Permission is hereby granted, free of charge, to any person obtaining a copy
7 | of this software and associated documentation files (the "Software"), to deal
8 | in the Software without restriction, including without limitation the rights
9 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
10 | copies of the Software, and to permit persons to whom the Software is
11 | furnished to do so, subject to the following conditions:
12 |
13 | The above copyright notice and this permission notice shall be included in
14 | all copies or substantial portions of the Software.
15 |
16 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
17 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
19 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
20 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
21 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
22 | THE SOFTWARE.
23 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |