Logo
Explore Help
Sign In
novox/mesh-delivery
Watch 19
Star 0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
cbdcf6da0ebd9ecb33ebe61ccebdf915d489b7fa
mesh-delivery/modules/mesh-delivery-forge-bridge/internal/bridge
T
History
jschoubben 2855ae7ebf Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A)
The forge's gitea_commit_status refuses the context mesh/check from R4e, so that only the checker's account, through
this bridge, can make a pull request pass the one required status.
2026-10-22 17:59:30 +02:00
..
acts_test.go
Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A)
2026-10-22 17:59:30 +02:00
acts.go
Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A)
2026-10-22 17:59:30 +02:00
bridge_test.go
Test the bridge's manifest and lock file conversion (issue 1448, design 47 R4c-2)
2026-10-20 18:53:07 +00:00
bridge.go
Read a merge's manifests and lock files at most eight at once, so a catalogue merge stays inside the bridge's bound (issues 1448, 1458, design 47 R4c-2)
2026-10-20 19:06:03 +00:00
files_test.go
Read a merge's manifests and lock files at most eight at once, so a catalogue merge stays inside the bridge's bound (issues 1448, 1458, design 47 R4c-2)
2026-10-20 19:06:03 +00:00
Powered by Gitea Version: 1.27.3 Page: 22ms Template: 2ms
Auto
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API