Size sign-off: https://github.com/bbl-dres/service-portal #6

New issue

Closed

opened 2026-09-14 01:33:50 +00:00 by mirror-sync · 1 comment

mirror-sync commented

2026-09-14 01:33:50 +00:00

Owner

https://github.com/bbl-dres/service-portal is listed by a source and was not imported: 292 MB upstream > 100 MB cap.

Size: 292 MB upstream
First held: 2026-09-14

Two ways to resolve this

Approve it — add https://github.com/bbl-dres/service-portal on a line of its own to mirrors/size_approvals.txt by pull request. The next scheduled run mirrors it and closes this ticket.

Keep it out — add it to the generator's exclusion list, also by pull request. A regenerate drops it from the set and this ticket closes with it.

Doing nothing leaves it held: it stays in every run report and is not mailed again.

Closing this ticket by hand is not a third way. Nothing about a close is remembered — the next run recomputes what is held, finds no open ticket for this repository, and files a new one, mails it again, and starts its waiting since date over. So closing this without changing the config is a request to be asked again from scratch, not a decision. Only the two changes above end the hold.

Either decision lands in versioned config, and only there. This ticket records it — a comment here changes nothing, so that the corpus stays rebuildable from the repository alone.

This ticket's title is how the scheduled job finds it — please do not edit it.

`https://github.com/bbl-dres/service-portal` is listed by a source and was **not imported**: 292 MB upstream > 100 MB cap. - Size: 292 MB upstream - First held: 2026-09-14 ## Two ways to resolve this **Approve it** — add `https://github.com/bbl-dres/service-portal` on a line of its own to [`mirrors/size_approvals.txt`](https://codeberg.org/open-source-ecosystem/opencode-forges/src/branch/main/mirrors/size_approvals.txt) by pull request. The next scheduled run mirrors it and closes this ticket. **Keep it out** — add it to the generator's exclusion list, also by pull request. A regenerate drops it from the set and this ticket closes with it. Doing nothing leaves it held: it stays in every run report and is not mailed again. **Closing this ticket by hand is not a third way.** Nothing about a close is remembered — the next run recomputes what is held, finds no open ticket for this repository, and files a new one, mails it again, and starts its *waiting since* date over. So closing this without changing the config is a request to be asked again from scratch, not a decision. Only the two changes above end the hold. Either decision lands in versioned config, and only there. This ticket records it — a comment here changes nothing, so that the corpus stays rebuildable from the repository alone. *This ticket's title is how the scheduled job finds it — please do not edit it.*

mirror-sync

2026-09-14 01:33:50 +00:00

closed this issue
added the
size-signoff
label

mirror-sync commented

2026-09-14 12:54:14 +00:00

Author

Owner

Closing: superseded by the organisation ticket for bbl-dres — that organisation does not exist on this instance yet, so nothing under it can be imported whatever its size. Its ticket lists this repository and is the one place to decide.

The decision itself lives in versioned config; this ticket only recorded it.

Closing: superseded by the organisation ticket for `bbl-dres` — that organisation does not exist on this instance yet, so nothing under it can be imported whatever its size. Its ticket lists this repository and is the one place to decide. The decision itself lives in versioned config; this ticket only recorded it.