Parents and children of check-in [5757eeaaeb]
|
2026-08-24
| ||
| 10:47 | merge people-admin into trunk check-in: f8af01dec3 user: dmestas tags: trunk | |
| 10:47 |
people: an admin sees which contributors are also accounts
A contributor is a name an author's client wrote on an artifact; an account is a login on this forge. On a mirror the two barely intersect — fossil has 151 contributors and this forge has two accounts, sharing none — so the page says so, and badges the few that are both. Read-only on purpose. A grant control here would offer to give write access to a string, and on a mirror those strings are chosen by whoever can commit upstream. The door goes to settings, where every row is a real account. account.list is forge-wide and site-admin only, so a repo admin gets the door without the badges rather than an error. closed check-in: 8fb0a669aa user: dmestas tags: people-admin | |
| 10:25 | merge repo-people into trunk check-in: 5757eeaaeb user: dmestas tags: trunk | |
| 10:25 |
people: a repository's contributors, inside the repository
"151 contributors" in fossil's About panel went to the fleet page: 481 names across 25 repositories, repo nav gone, search rescoped to the whole forge. people.list has taken a repo parameter all along and nothing in the UI reached it. The per-person line differs from the fleet's on purpose. Counting repositories inside one repository always says 1, so the span of somebody's work here is the fact worth carrying instead. Contributors(0) meant a hundred, silently, which is why the listing said "of 100" under an About panel saying 151. It means all of them now. closed check-in: 278e021086 user: dmestas tags: repo-people | |
| 09:52 | merge landing mimetype with trunk check-in: cfd042dd99 user: dmestas tags: trunk | |