| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-11-28 | fix maintainer recursion | DanConwayDev | |
| 2025-11-28 | sync HEAD on state event and git data push | DanConwayDev | |
| 2025-11-28 | add git http advertisment allow-reachable-sha1-in-want and ↵ | DanConwayDev | |
| allow-tip-sha1-in-want | |||
| 2025-11-27 | refactor(auth): simplify state auth with single-query approach | DanConwayDev | |
| 2025-11-27 | fix(auth): accept state announcements from maintainers | DanConwayDev | |
| Updated get_maintainers_recursive() to properly handle maintainers listed in accepted repository announcements: 1. Separated 'visited' set (cycle prevention) from 'maintainers' set (result) 2. Maintainers listed in an announcement's 'maintainers' tag are now added to the maintainer set immediately, even without their own announcement 3. Recursively traverse maintainer chains to handle multi-level delegation Also fixed RecursiveMaintainerRepoAndState fixture to publish the maintainer's announcement (which lists the recursive maintainer) before publishing the recursive maintainer's announcement, establishing the proper trust chain: Owner -> Maintainer -> RecursiveMaintainer Test results: 7/7 push authorization tests passing | |||
| 2025-11-26 | fix: parsing maintainers from announcement event | DanConwayDev | |
| 2025-11-26 | feat: push authorization from state event | DanConwayDev | |
| 2025-11-21 | fixed http clone | DanConwayDev | |
| but do we really nedd to create a blank commit? I dont think ngit-relay does that. Do we need to se the default branch or is this automatic? | |||
| 2025-11-21 | add git http handling | DanConwayDev | |