Size sign-off: https://github.com/bbl-dres/data-catalog #10

New issue

Closed

opened 2026-09-15 08:35:44 +00:00 by mirror-sync · 1 comment

mirror-sync commented

2026-09-15 08:35:44 +00:00

Owner

https://github.com/bbl-dres/data-catalog is listed by a source and was not imported: just over the 100 MB cap (103018 KB > 102400 KB).

Size: 100 MB upstream
First held: 2026-09-15

Two ways to resolve this, both done on this ticket

Approve it — apply the approve label. The next scheduled run writes https://github.com/bbl-dres/data-catalog into config/size_approvals.txt, mirrors the repository, and closes this ticket as approved.

Decline it — close this ticket. The next run records that in config/repo_declines.txt pointing back here and relabels it declined, so the closed ticket is the public answer to why isn't this on the platform?. Leave a comment saying why before you close — the file records the decision and links to this ticket, so this ticket is where the reason has to live. Changed your mind? Reopen it: the next run withdraws the line and the question comes back.

Doing nothing leaves it held: it stays in every run report and is not mailed again. That is a decision nobody can read, which is what a recorded decline avoids.

A decline mutes the ask; it does not delete anything. For this repository that is the whole story — the size gate is what holds it, and it keeps holding. To keep a repository below the cap out, the generator's exclusion list is the only thing that works, and that one is a pull request against the source repository.

Both decisions are carried out by the scheduled run, not at the moment you click. Until it next runs, the label or the closure is a request on record and nothing has happened yet.

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

`https://github.com/bbl-dres/data-catalog` is listed by a source and was **not imported**: just over the 100 MB cap (103018 KB > 102400 KB). - Size: 100 MB upstream - First held: 2026-09-15 ## Two ways to resolve this, both done on this ticket **Approve it** — apply the `approve` label. The next scheduled run writes `https://github.com/bbl-dres/data-catalog` into `config/size_approvals.txt`, mirrors the repository, and closes this ticket as `approved`. **Decline it** — close this ticket. The next run records that in `config/repo_declines.txt` pointing back here and relabels it `declined`, so the closed ticket is the public answer to *why isn't this on the platform?*. **Leave a comment saying why before you close** — the file records the decision and links to this ticket, so this ticket is where the reason has to live. Changed your mind? Reopen it: the next run withdraws the line and the question comes back. Doing nothing leaves it held: it stays in every run report and is not mailed again. That is a decision nobody can read, which is what a recorded decline avoids. **A decline mutes the ask; it does not delete anything.** For this repository that is the whole story — the size gate is what holds it, and it keeps holding. To keep a repository *below* the cap out, the generator's exclusion list is the only thing that works, and that one is a pull request against the source repository. Both decisions are carried out by the scheduled run, not at the moment you click. Until it next runs, the label or the closure is a request on record and nothing has happened yet. *This ticket's title is how the scheduled job finds it — please do not edit it.*

mirror-sync added the

size-signoff

label

2026-09-15 08:35:44 +00:00

forgejo_admin added the

approve

label

2026-09-15 09:35:14 +00:00

mirror-sync added the

approved

label

2026-09-15 11:38:13 +00:00

mirror-sync referenced this issue from a commit

2026-09-15 11:38:14 +00:00

approve https://github.com/bbl-dres/data-catalog (#10)

mirror-sync closed this issue

2026-09-15 11:39:33 +00:00

mirror-sync commented

2026-09-15 11:39:33 +00:00

Author

Owner

Closing: approved in size_approvals.txt — the import runs with the next full pass, if it did not already run later in this one.

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

Closing: approved in `size_approvals.txt` — the import runs with the next full pass, if it did not already run later in this one. The decision itself lives in versioned config; this ticket only recorded it.