Thamognya Kodi 6 months ago
commit 434fbb342f
  1. 778
  2. 24
  3. 17
  4. 1
  5. 76
  6. 47
  7. 42
  8. 3
  9. 23
  10. 25
  11. 28
  12. 399
  13. 27
  14. 35
  15. 28
  16. 42
  17. 16
  18. 16
  19. 778
  20. 44
  21. 8
  22. 663
  23. 123
  24. 1
  25. 21
  26. 25
  27. 47
  28. 13
  29. 17
  30. 0
  31. 0
  32. 0
  33. 1
  34. 14
  35. 67
  36. 0
  37. 0
  38. 2
  39. 2756
  40. 154
  41. 55
  42. 3
  43. 8
  44. 4
  45. 3
  46. 0
  47. 0
  48. 0
  49. 0
  50. 0
  51. 0
  52. 3

@ -0,0 +1,778 @@
# Created by,python,pycharm,windows,visualstudio,visualstudiocode
# Edit at,python,pycharm,windows,visualstudio,visualstudiocode
### OSX ###
# General
# Icon must end with two \r
# Thumbnails
# Files that might appear in the root of a volume
# Directories potentially created on remote AFP share
Network Trash Folder
Temporary Items
### PyCharm ###
# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and WebStorm
# Reference:
# User-specific stuff
# Generated files
# Sensitive or high-churn files
# Gradle
# Gradle and Maven with auto-import
# When using Gradle or Maven with auto-import, you should exclude module files,
# since they will be recreated, and may cause churn. Uncomment if using
# auto-import.
# .idea/modules.xml
# .idea/*.iml
# .idea/modules
# *.iml
# *.ipr
# CMake
# Mongo Explorer plugin
# File-based project format
# IntelliJ
# mpeltonen/sbt-idea plugin
# JIRA plugin
# Cursive Clojure plugin
# Crashlytics plugin (for Android Studio and IntelliJ)
# Editor-based Rest Client
# Android studio 3.1+ serialized cache file
### PyCharm Patch ###
# Comment Reason:
# *.iml
# modules.xml
# .idea/misc.xml
# *.ipr
# Sonarlint plugin
# SonarQube Plugin
# Markdown Navigator plugin
### Python ###
# Byte-compiled / optimized / DLL files
# C extensions
# Distribution / packaging
# PyInstaller
# Usually these files are written by a python script from a template
# before PyInstaller builds the exe, so as to inject date/other infos into it.
# Installer logs
# Unit test / coverage reports
# Translations
# Scrapy stuff:
# Sphinx documentation
# PyBuilder
# pyenv
# poetry
# pipenv
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
# celery beat schedule file
# SageMath parsed files
# Spyder project settings
# Rope project settings
# Mr Developer
# mkdocs documentation
# mypy
# Pyre type checker
# Plugins
### VisualStudioCode ###
### VisualStudioCode Patch ###
# Ignore all local history of files
### Windows ###
# Windows thumbnail cache files
# Dump file
# Folder config file
# Recycle Bin used on file shares
# Windows Installer files
# Windows shortcuts
### VisualStudio ###
## Ignore Visual Studio temporary files, build results, and
## files generated by popular Visual Studio add-ons.
## Get latest from
# User-specific files
# User-specific files (MonoDevelop/Xamarin Studio)
# Mono auto generated files
# Build results
# Visual Studio 2015/2017 cache/options directory
# Uncomment if you have tasks that create the project's static files in wwwroot
# Visual Studio 2017 auto generated files
Generated\ Files/
# MSTest test Results
# NUnit
# Build Results of an ATL Project
# Benchmark Results
# .NET Core
# StyleCop
# Files built by Visual Studio
# Chutzpah Test files
# Visual C++ cache files
# Visual Studio profiler
# Visual Studio Trace Files
# TFS 2012 Local Workspace
# Guidance Automation Toolkit
# ReSharper is a .NET coding add-in
# JustCode is a .NET coding add-in
# TeamCity is a build add-in
# DotCover is a Code Coverage Tool
# AxoCover is a Code Coverage Tool
# Visual Studio code coverage results
# NCrunch
# MightyMoose
# Web workbench (sass)
# Installshield output folder
# DocProject is a documentation generator add-in
# Click-Once directory
# Publish Web Output
# Note: Comment the next line if you want to checkin your web deploy settings,
# but database connection strings (with potential passwords) will be unencrypted
# Microsoft Azure Web App publish settings. Comment the next line if you want to
# checkin your Azure Web App publish settings, but sensitive information contained
# in these scripts will be unencrypted
# NuGet Packages
# NuGet Symbol Packages
# The packages folder can be ignored because of Package Restore
# except build/, which is used as an MSBuild target.
# Uncomment if necessary however generally it will be regenerated when needed
# NuGet v3's project.json files produces more ignorable files
# Microsoft Azure Build Output
# Microsoft Azure Emulator
# Windows Store app package directories and files
# Visual Studio cache files
# files ending in .cache can be ignored
# but keep track of directories ending in .cache
# Others
# Including strong name files can present a security risk
# (
# Since there are multiple workflows, uncomment next line to ignore bower_components
# (
# RIA/Silverlight projects
# Backup & report files from converting an old project file
# to a newer Visual Studio version. Backup files are not needed,
# because we have git ;-)
# SQL Server files
# Business Intelligence projects
*- [Bb]ackup.rdl
*- [Bb]ackup ([0-9]).rdl
*- [Bb]ackup ([0-9][0-9]).rdl
# Microsoft Fakes
# GhostDoc plugin setting file
# Node.js Tools for Visual Studio
# Visual Studio 6 build log
# Visual Studio 6 workspace options file
# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)
# Visual Studio LightSwitch build output
# Paket dependency manager
# FAKE - F# Make
# CodeRush personal settings
# Python Tools for Visual Studio (PTVS)
# Cake - Uncomment if you are using it
# tools/**
# !tools/packages.config
# Tabs Studio
# Telerik's JustMock configuration file
# BizTalk build output
# OpenCover UI analysis results
# Azure Stream Analytics local run output
# MSBuild Binary and Structured Log
# NVidia Nsight GPU debugger configuration file
# MFractors (Xamarin productivity tool) working folder
# Local History for Visual Studio
# BeatPulse healthcheck temp database
# Backup folder for Package Reference Convert tool in Visual Studio 2017
# End of,python,pycharm,windows,visualstudio,visualstudiocode
# Byte-compiled / optimized / DLL files
# C extensions
# Distribution / packaging
# PyInstaller
# Usually these files are written by a python script from a template
# before PyInstaller builds the exe, so as to inject date/other infos into it.
# Installer logs
# Unit test / coverage reports
# Translations
# Django stuff:
# Flask stuff:
# Scrapy stuff:
# Sphinx documentation
# PyBuilder
# Jupyter Notebook
# IPython
# pyenv
# For a library or package, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in:
# .python-version
# pipenv
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
# poetry
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
# This is especially recommended for binary packages to ensure reproducibility, and is more
# commonly ignored for libraries.
# pdm
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
# in version control.
# PEP 582; used by e.g. and
# Celery stuff
# SageMath parsed files
# Environments
# Spyder project settings
# Rope project settings
# mkdocs documentation
# mypy
# Pyre type checker
# pytype static type analyzer
# Cython debug symbols
# PyCharm
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
# be found at
# and can be added to the global gitignore or merged into this file. For a more nuclear
# option (not recommended) you can uncomment the following to ignore the entire idea folder.

@ -0,0 +1,24 @@
# Check for more information
# This is the main config file for this project:
root = true
charset = utf-8
end_of_line = lf
insert_final_newline = true
indent_style = space
indent_size = 4
trim_trailing_whitespace = true
[*.{py, pyi}]
indent_style = space
indent_size = 4
indent_style = tab
trim_trailing_whitespace = false
trim_trailing_whitespace = false

@ -0,0 +1,17 @@
# Number of days of inactivity before an issue becomes stale
daysUntilStale: 60
# Number of days of inactivity before a stale issue is closed
daysUntilClose: 7
# Issues with these labels will never be considered stale
- pinned
- security
# Label to use when marking an issue as stale
staleLabel: wontfix
# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: false

@ -0,0 +1 @@
* @thamognya

@ -0,0 +1,76 @@
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, nationality, personal
appearance, race, religion, or sexual identity and orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at
For answers to common questions about this code of conduct, see

@ -0,0 +1,47 @@
# How to contribute
## Dependencies
We use `poetry` to manage the [dependencies](
If you dont have `poetry`, you should install with `make poetry-download`.
To install dependencies and prepare [`pre-commit`]( hooks you would need to run `install` command:
make install
make pre-commit-install
To activate your `virtualenv` run `poetry shell`.
## Codestyle
After installation you may execute code formatting.
make codestyle
### Checks
Many checks are configured for this project. Command `make check-codestyle` will check black, isort and darglint.
The `make check-safety` command will look at the security of your code.
Comand `make lint` applies all checks.
### Before submitting
Before submitting your code please do the following steps:
1. Add any changes you want
1. Add tests for the new changes
1. Edit documentation if you have changed something significant
1. Run `make codestyle` to format your changes.
1. Run `make lint` to ensure that types, security and docstrings are okay.
## Other help
You can contribute by spreading a word about this library.
It would also be a huge contribution to write
a short article on how you are using this project.
You can also share your best practices with us.

@ -0,0 +1,42 @@
name: πŸ› Bug report
about: If something isn't working πŸ”§
title: ''
labels: bug
## πŸ› Bug Report
<!-- A clear and concise description of what the bug is. -->
## πŸ”¬ How To Reproduce
Steps to reproduce the behavior:
1. ...
### Code sample
<!-- If applicable, attach a minimal code sample to reproduce the decried issue. -->
### Environment
* OS: [e.g. Linux / Windows / macOS]
* Python version, get it with:
python --version
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
## πŸ“ˆ Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
## πŸ“Ž Additional context
<!-- Add any other context about the problem here. -->

@ -0,0 +1,3 @@
# Configuration:
blank_issues_enabled: false

@ -0,0 +1,23 @@
name: πŸš€ Feature request
about: Suggest an idea for this project πŸ–
title: ''
labels: enhancement
## πŸš€ Feature Request
<!-- A clear and concise description of the feature proposal. -->
## πŸ”ˆ Motivation
<!-- Please describe the motivation for this proposal. -->
## πŸ›° Alternatives
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
## πŸ“Ž Additional context
<!-- Add any other context or screenshots about the feature request here. -->

@ -0,0 +1,25 @@
name: ❓ Question
about: Ask a question about this project πŸŽ“
title: ''
labels: question
## Checklist
<!-- Mark with an `x` all the checkboxes that apply (like `[x]`) -->
- [ ] I've searched the project's [`issues`](
## ❓ Question
<!-- What is your question -->
How can I [...]?
Is it possible to [...]?
## πŸ“Ž Additional context
<!-- Add any other context or screenshots about the feature request here. -->

@ -0,0 +1,28 @@
## Description
<!-- Add a more detailed description of the changes if needed. -->
## Related Issue
<!-- If your PR refers to a related issue, link it here. -->
## Type of Change
<!-- Mark with an `x` all the checkboxes that apply (like `[x]`) -->
- [ ] πŸ“š Examples / docs / tutorials / dependencies update
- [ ] πŸ”§ Bug fix (non-breaking change which fixes an issue)
- [ ] πŸ₯‚ Improvement (non-breaking change which improves an existing feature)
- [ ] πŸš€ New feature (non-breaking change which adds functionality)
- [ ] πŸ’₯ Breaking change (fix or feature that would cause existing functionality to change)
- [ ] πŸ” Security fix
## Checklist
<!-- Mark with an `x` all the checkboxes that apply (like `[x]`) -->
- [ ] I've read the [``]( document.
- [ ] I've read the [``]( guide.
- [ ] I've updated the code style using `make codestyle`.
- [ ] I've written tests for all new methods and classes that I created.
- [ ] I've written the docstring in Google format for all the methods and classes that I used.

@ -0,0 +1,399 @@
# Internet-ML: Allowing ML to connect to the internet
<div align="center">
[![Build status](](
[![Python Version](](
[![Dependencies Status](](
[![Code style: black](](
[![Security: bandit](](
[![Semantic Versions](](
![Coverage Report](assets/images/coverage.svg)
## Very first steps
### Initialize your code
1. Initialize `git` inside your repo:
cd internet-ml && git init
2. If you don't have `Poetry` installed run:
make poetry-download
3. Initialize poetry and install `pre-commit` hooks:
make install
make pre-commit-install
4. Run the codestyle:
make codestyle
5. Upload initial code to GitHub:
git add .
git commit -m ":tada: Initial commit"
git branch -M main
git remote add origin
git push -u origin main
### Set up bots
- Set up [Dependabot]( to ensure you have the latest dependencies.
- Set up [Stale bot]( for automatic issue closing.
### Poetry
Want to know more about Poetry? Check [its documentation](
<summary>Details about Poetry</summary>
Poetry's [commands]( are very intuitive and easy to learn, like:
- `poetry add numpy@latest`
- `poetry run pytest`
- `poetry publish --build`
### Building and releasing your package
Building a new version of the application contains steps:
- Bump the version of your package `poetry version <version>`. You can pass the new version explicitly, or a rule such as `major`, `minor`, or `patch`. For more details, refer to the [Semantic Versions]( standard.
- Make a commit to `GitHub`.
- Create a `GitHub release`.
- And... publish πŸ™‚ `poetry publish --build`
## 🎯 What's next
Well, that's up to you πŸ’ͺ🏻. I can only recommend the packages and articles that helped me.
- [`Typer`]( is great for creating CLI applications.
- [`Rich`]( makes it easy to add beautiful formatting in the terminal.
- [`Pydantic`]( – data validation and settings management using Python type hinting.
- [`Loguru`]( makes logging (stupidly) simple.
- [`tqdm`]( – fast, extensible progress bar for Python and CLI.
- [`IceCream`]( is a little library for sweet and creamy debugging.
- [`orjson`]( – ultra fast JSON parsing library.
- [`Returns`]( makes you function's output meaningful, typed, and safe!
- [`Hydra`]( is a framework for elegantly configuring complex applications.
- [`FastAPI`]( is a type-driven asynchronous web framework.
- [Open Source Guides](
- [A handy guide to financial support for open source](
- [GitHub Actions Documentation](
- Maybe you would like to add [gitmoji]( to commit names. This is really funny. πŸ˜„
## πŸš€ Features
### Development features
- Supports for `Python 3.11` and higher.
- [`Poetry`]( as the dependencies manager. See configuration in [`pyproject.toml`]( and [`setup.cfg`](
- Automatic codestyle with [`black`](, [`isort`]( and [`pyupgrade`](
- Ready-to-use [`pre-commit`]( hooks with code-formatting.
- Type checks with [`mypy`](; docstring checks with [`darglint`](; security checks with [`safety`]( and [`bandit`](
- Testing with [`pytest`](
- Ready-to-use [`.editorconfig`](, [`.dockerignore`](, and [`.gitignore`]( You don't have to worry about those things.
### Deployment features
- `GitHub` integration: issue and pr templates.
- `Github Actions` with predefined [build workflow]( as the default CI/CD.
- Everything is already set up for security checks, codestyle checks, code formatting, testing, linting, docker builds, etc with [`Makefile`]( More details in [makefile-usage](#makefile-usage).
- [Dockerfile]( for your package.
- Always up-to-date dependencies with [`@dependabot`]( You will only [enable it](
- Automatic drafts of new releases with [`Release Drafter`]( You may see the list of labels in [`release-drafter.yml`]( Works perfectly with [Semantic Versions]( specification.
### Open source community features
- Ready-to-use [Pull Requests templates]( and several [Issue templates](
- Files such as: `LICENSE`, ``, ``, and `` are generated automatically.
- [`Stale bot`]( that closes abandoned issues after a period of inactivity. (You will only [need to setup free plan]( Configuration is [here](
- [Semantic Versions]( specification with [`Release Drafter`](
## Installation
pip install -U internet-ml
or install with `Poetry`
poetry add internet-ml
Then you can run
internet-ml --help
or with `Poetry`:
poetry run internet-ml --help
### Makefile usage
[`Makefile`]( contains a lot of functions for faster development.
<summary>1. Download and remove Poetry</summary>
To download and install Poetry run:
make poetry-download
To uninstall
make poetry-remove
<summary>2. Install all dependencies and pre-commit hooks</summary>
Install requirements:
make install
Pre-commit hooks coulb be installed after `git init` via
make pre-commit-install
<summary>3. Codestyle</summary>
Automatic formatting uses `pyupgrade`, `isort` and `black`.
make codestyle
# or use synonym
make formatting
Codestyle checks only, without rewriting files:
make check-codestyle
> Note: `check-codestyle` uses `isort`, `black` and `darglint` library
Update all dev libraries to the latest version using one comand
make update-dev-deps
<summary>4. Code security</summary>
make check-safety
This command launches `Poetry` integrity checks as well as identifies security issues with `Safety` and `Bandit`.
make check-safety
<summary>5. Type checks</summary>
Run `mypy` static type checker
make mypy
<summary>6. Tests with coverage badges</summary>
Run `pytest`
make test
<summary>7. All linters</summary>
Of course there is a command to ~~rule~~ run all linters in one:
make lint
the same as:
make test && make check-codestyle && make mypy && make check-safety
<summary>8. Docker</summary>
make docker-build
which is equivalent to:
make docker-build VERSION=latest
Remove docker image with
make docker-remove
More information [about docker](
<summary>9. Cleanup</summary>
Delete pycache files
make pycache-remove
Remove package build
make build-remove
Delete .DS_STORE files
make dsstore-remove
Remove .mypycache
make mypycache-remove
Or to remove all above run:
make cleanup
## πŸ“ˆ Releases
You can see the list of available releases on the [GitHub Releases]( page.
We follow [Semantic Versions]( specification.
We use [`Release Drafter`]( As pull requests are merged, a draft release is kept up-to-date listing the changes, ready to publish when you’re ready. With the categories option, you can categorize pull requests in release notes using labels.
### List of labels and corresponding titles
| **Label** | **Title in Releases** |
| :-----------------------------------: | :---------------------: |
| `enhancement`, `feature` | πŸš€ Features |
| `bug`, `refactoring`, `bugfix`, `fix` | πŸ”§ Fixes & Refactoring |
| `build`, `ci`, `testing` | πŸ“¦ Build System & CI/CD |
| `breaking` | πŸ’₯ Breaking Changes |
| `documentation` | πŸ“ Documentation |
| `dependencies` | ⬆️ Dependencies updates |
You can update it in [`release-drafter.yml`](
GitHub creates the `bug`, `enhancement`, and `documentation` labels for you. Dependabot creates the `dependencies` label. Create the remaining labels on the Issues tab of your GitHub repository, when you need them.
## πŸ›‘ License
This project is licensed under the terms of the `GNU GPL v3.0` license. See [LICENSE]( for more details.
## πŸ“ƒ Citation
author = {Thamognya Kodi},
title = {Internet-ML: Allowing ML to connect to the internet},
year = {2022},
publisher = {GitHub},
journal = {GitHub repository},
howpublished = {\url{}}

@ -0,0 +1,27 @@
# Security
## πŸ” Reporting Security Issues
> Do not open issues that might have security implications!
> It is critical that security related issues are reported privately so we have time to address them before they become public knowledge.
Vulnerabilities can be reported by emailing core members:
- internet-ml [](
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Environment (e.g. Linux / Windows / macOS)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
## Preferred Languages
We prefer all communications to be in English.

@ -0,0 +1,35 @@
# Configuration:
# Docs:
version: 2
- package-ecosystem: "pip"
directory: "/"
interval: "daily"
- dependency-type: "all"
prefix: ":arrow_up:"
open-pull-requests-limit: 50
- package-ecosystem: "github-actions"
directory: "/"
interval: "daily"
- dependency-type: "all"
prefix: ":arrow_up:"
open-pull-requests-limit: 50
- package-ecosystem: "docker"
directory: "/docker"
interval: "weekly"
- dependency-type: "all"
prefix: ":arrow_up:"
open-pull-requests-limit: 50

@ -0,0 +1,28 @@
# Release drafter configuration
# Emojis were chosen to match the
name-template: "v$NEXT_PATCH_VERSION"
tag-template: "v$NEXT_PATCH_VERSION"
- title: ":rocket: Features"
labels: [enhancement, feature]
- title: ":wrench: Fixes & Refactoring"
labels: [bug, refactoring, bugfix, fix]
- title: ":package: Build System & CI/CD"
labels: [build, ci, testing]
- title: ":boom: Breaking Changes"
labels: [breaking]
- title: ":pencil: Documentation"
labels: [documentation]
- title: ":arrow_up: Dependencies updates"
labels: [dependencies]
template: |
## What’s Changed
## :busts_in_silhouette: List of contributors

@ -0,0 +1,42 @@
name: build
on: [push, pull_request]
runs-on: ubuntu-latest
python-version: ["3.11", "3.9"]
- uses: actions/checkout@v2
- name: Set up Python ${{ matrix.python-version }}
uses: actions/setup-python@v2.2.2
python-version: ${{ matrix.python-version }}
- name: Install poetry
run: make poetry-download
- name: Set up cache
uses: actions/cache@v2.1.6
path: .venv
key: venv-${{ matrix.python-version }}-${{ hashFiles('pyproject.toml') }}-${{ hashFiles('poetry.lock') }}
- name: Install dependencies
run: |
poetry config true
poetry install
- name: Run style checks
run: |
make check-codestyle
- name: Run tests
run: |
make test
- name: Run safety checks
run: |
make check-safety

@ -0,0 +1,16 @@
name: Greetings
on: [pull_request, issues]
runs-on: ubuntu-latest
- uses: actions/first-interaction@v1
repo-token: ${{ secrets.GITHUB_TOKEN }}
pr-message: 'Hello @${{ }}, thank you for submitting a PR! We will respond as soon as possible.'
issue-message: |
Hello @${{ }}, thank you for your interest in our work!
If this is a bug report, please provide screenshots and **minimum viable code to reproduce your issue**, otherwise we can not help you.