Add recurring full CI and protected contributor routes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
Research direction
Start with the existing full CI workflow and devguide/pending_bugs/recurring_full_ci_and_contributor_routes.md. Review the current source-pinned environment, stable checks, and external PR integration before defining the scheduled, manual, macOS arm64, and daily recovery paths. Done means hosted evidence covers zero debt, skipped debt, and full recovery while preserving the direct-push route and supported Python range.
Written by the indexing model from the issue text.
Description
DockingMT independent receiving — 2026-10-09
CI and distribution remain partial. Current source a2b282a4ea1afa4524e92cbb4a444c0c6fe1dad8 passes all seven CI jobs, policy and Conda controls. All four Linux Python 3.11–3.14 suites execute; 3.14 has 1037 passed.
Actual daily recovery 37794015785, at older source edc7ce1d8c6b8e216454d28eaf6de65cb24b8226, detects one skipped commit and passes all six configured full cells (Linux 3.11–3.14 and macOS arm64 3.13/3.14; both 3.14 cells: 1000 passed). Daily 37943924984 observes zero skips and intentionally omits tests. Probe 37844141027 detects two skips but does not run science or clear debt. These observations are source-scoped, not current-head recovery evidence.
Historical internal LMMV PR uibcdf/dockingmt#20 passes four jobs, including then-supported Linux 3.11–3.13 (3.13: 103 passed). Requested head ac91b224 actually tests synthetic integration 5a21a4f47e484f96ec51d399b45c929a0ffd380f. Current four-minor/preflight PR execution and an external actor are not inferred. Protection retains five strict quality/Linux checks, explicit PR integration and the authorized admin exemption.
Thirteen accepted recovery/publication inputs remain byte-identical; 59 mandatory payload paths are retained. uibcdf/molsyssuite#110 is delivered at 948d0267de8fa43c542ab7eba28b9f8b7fbf095e, but its accepted handoff requires a real installed candidate before adopting the pin/removing the installed-only workaround. There is no real release plan: version selection, exact candidate gates, all eight installed cells and same-byte public receiving remain uibcdf/dockingmt#47; public platform/admission review remains uibcdf/dockingmt#30. Coverage uibcdf/dockingmt#22 is already closed.
Immutable receiving receipt. Local: six tests and offline guard passed. Exact central commit validation, attempt 1: 447 tests, governance, publisher controls, retained XML and coverage upload passed. No component files, scientific assertions, versions, pins or publication operations changed. Global private-OpenCASTp audits remain a separate uibcdf/molsyssuite#102 access limitation.
Previous issue context (retained)
What — DockingMT runs its full Linux Python 3.11–3.13 suite on pushes and PRs, but has no recurring matrix, daily recovery of CI-skip commits, or protection of the external PR route.
How — Preserve the existing source-pinned dependency environment and full CI. Add weekly/manual full Linux coverage and a macOS arm64 Python 3.13 representative, plus a conditional daily detector that retains skipped-commit debt until an executed green full Linux matrix. Require existing stable checks and PR integration for external contributions, preserving the dprada/LMMV admin direct-push route. Record hosted zero-debt, skipped-debt, and full recovery evidence.
Why — Implements uibcdf/molsyssuite#39 without changing scientific assertions or the component's supported Python range. At ac91b22, CI run 36349574106 passed, but the workflow only has push/PR triggers and main is not protected. Both current collaborators are administrators dprada and LMMV.
Record — devguide/pending_bugs/recurring_full_ci_and_contributor_routes.md
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 30m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uibcdf/dockingmt
-
proposal
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
component:molsysmt
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
partial proposal
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
component:molsysmt enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
component:molsysmt component:molsysviewer enhancement partial
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in uibcdf/dockingmt
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Deltares/imod-python#1940 ·
Maintainers usually reply within 1 day
-
effort: low prio: low ready
Difficulty 1/5 Under an hour Newbie friendliness 82/100
digitalfabrik/integreat-cms#4621 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ioos/compliance-checker#1375 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
netbox status: backlog topic: testing type: housekeeping
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
netbox-community/netbox#23395 ·
Maintainers usually reply within 1 day