alissa-tools-github-revloop
The alissa.tools.github.revloop module: a GitHub watcher that drives the
alissa-code-review adversarial review loop (CR1–CR9) to convergence.
This distribution ships only that module. Everything above it —
alissa, alissa.tools, alissa.tools.github — is a
PEP 420 namespace package with no
__init__.py, so other distributions in other repositories can contribute
their own packages under the same namespace:
alissa/ ← namespace (no __init__.py)
└── tools/ ← namespace
├── github/ ← namespace
│ ├── revloop/ __init__.py ← THIS distribution
│ └── issues/ __init__.py ← could ship from another repo
└── slack/ ← namespace
└── notify/ __init__.py ← could ship from another repo
The rule: a distribution owns a leaf package and declares only that subtree
(find_namespace_packages(include=[PACKAGE, f"{PACKAGE}.*"])). Adding an
__init__.py at any namespace level would claim it for one distribution and
shadow the others.
Discovery PRs are not reviewed
A PR in a plans repository (plan_repos, ALISSA_REVIEW_PLAN_REPOS) whose
body carries <!-- alissa-discovery v1 --> on a line of its own and whose
every changed path is under knowledge-base/ gets no review round — no
reviewer session, no review task — and one activity-comment line per head
saying why. A marked PR that touches anything else (or whose file list cannot
be read in full) is reviewed under the code directive, unchanged. The fleet
flag discovery_review (ALISSA_REVIEW_DISCOVERY_REVIEW, default off) turns
the skip off: every discovery PR is then reviewed like any other. See
Discovery PRs in the repository README.
Install
pip install -e ./alissa-tools-github-revloop
Console scripts
| Command | Entry point |
|---|---|
alissa-revloop |
alissa.tools.github.revloop.__main__:main |
Layout
src/main holds the package tree, src/test mirrors it as test_*. The
distribution version lives in the plain-text version file next to the module
it versions (src/main/alissa/tools/github/revloop/version), read by both
setup.py and version.py.
License
Licensed under the Apache License 2.0 — see the LICENSE and NOTICE files
shipped with this distribution.
"Alissa" and "Fahera" are trademarks of CORE FAHERA ENTERPRISE HOLDINGS S. DE R.L.; the license does not grant permission to use them.
1 maintainer
Metadata
1 maintainer
Release files for alissa-tools-github-revloop 0.31.20
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| alissa_tools_github_revloop-0.31.20.tar.gz | 367.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| alissa_tools_github_revloop-0.31.20-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 750.2 kB
Release files / alissa_tools_github_revloop-0.31.20.tar.gz
| Download URL | alissa_tools_github_revloop-0.31.20.tar.gz |
|---|---|
| Size | 367.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a088aa325ea32bc806ce89e85015ab8be7298090cfba6b04f5b382d512223747
|
|
BLAKE2b-256 checksum How to use checksums |
31096139d128ccdb3d71523ac074c66cb32b93ad20a099cf6c9fabb7554a848b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / alissa_tools_github_revloop-0.31.20-py3-none-any.whl
| Download URL | alissa_tools_github_revloop-0.31.20-py3-none-any.whl |
|---|---|
| Size | 383.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6cabf4b53ca4b6d8bb71a3549520ca524da542aa3a98b0cf851c93c5c164b735
|
|
BLAKE2b-256 checksum How to use checksums |
18fdbe2fb52668aee1de55f2687fe3eceb56808871e86b5319e3a3538d35650d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for alissa-tools-github-revloop 0.31.20
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
