Post 9x3SANEzc7gOdOsZdI by klardotsh@toot.cafe
 (DIR) More posts by klardotsh@toot.cafe
 (DIR) Post #9x3Pfr5APjYSIibSHQ by sir@cmpwn.com
       2020-07-13T20:17:12Z
       
       0 likes, 0 repeats
       
       There's something interesting on this page https://lists.sr.ht/~sircmpwn/scdoc-test/patches/11594
       
 (DIR) Post #9x3PwjM0OwXTFqWfkO by tristan957@mastodon.social
       2020-07-13T20:19:48Z
       
       0 likes, 0 repeats
       
       @sir congrats on landing the feature
       
 (DIR) Post #9x3Q6mpeKBQWwCBdwm by nloomans@mastodon.technology
       2020-07-13T20:20:45Z
       
       0 likes, 0 repeats
       
       @sir holy cow, yass! I love it!How do you detect the correct repo to apply the patch to?
       
 (DIR) Post #9x3QE2H9IvDCrVVReC by sir@cmpwn.com
       2020-07-13T20:23:13Z
       
       0 likes, 0 repeats
       
       @nloomans if you use [PATCH projectname], it'll look for a repo on the same (hub.sr.ht) project and assume it's for that. I have some ideas about testing patch applicability to investigate in the future as well
       
 (DIR) Post #9x3QMAwMyLeW3IfTs0 by wolf480pl@mstdn.io
       2020-07-13T20:25:51Z
       
       0 likes, 0 repeats
       
       @sir >Forward this thread to me
       
 (DIR) Post #9x3QVkzmI3K6TspaeO by sir@cmpwn.com
       2020-07-13T20:27:10Z
       
       0 likes, 0 repeats
       
       @wolf480pl that is fairly new, but that's not what I added today
       
 (DIR) Post #9x3QzDV7O1MzHrXP0q by nloomans@mastodon.technology
       2020-07-13T20:31:37Z
       
       0 likes, 0 repeats
       
       @sir Ah so you always need a prefix, even when the list has only one repo attached to it?
       
 (DIR) Post #9x3R6cqbXyHpvQ7XjE by sir@cmpwn.com
       2020-07-13T20:32:19Z
       
       0 likes, 0 repeats
       
       @nloomans aye. Reason being that you might share one list among several projects, like your public inbox
       
 (DIR) Post #9x3RLk5uswHekFUVBQ by wolf480pl@mstdn.io
       2020-07-13T20:36:59Z
       
       0 likes, 0 repeats
       
       @sir builds autoreply?
       
 (DIR) Post #9x3SANEzc7gOdOsZdI by klardotsh@toot.cafe
       2020-07-13T20:44:26Z
       
       0 likes, 0 repeats
       
       @sir very nice!are there (or are you thinking of) ways to disable the CI auto-run until the patch is in some "Approved for CI" state to prevent malicious (or even accidental) secret leakage?something like ^ would actually be better than the usual CI flow on GitHub/GitLab, where I have to outright disable CI secrets on forked repos (because, well, duh)... which means I can't run a full, true CI stack on inbound PRs unless I adopt the tree (and rebase the PR) into the upstream repo...
       
 (DIR) Post #9x3SfYNKGZu490e1UO by sir@cmpwn.com
       2020-07-13T20:50:48Z
       
       0 likes, 0 repeats
       
       @klardotsh these builds are submitted with secrets disabled. Same is true of dispatch.sr.ht's integration with github pull requests, actually
       
 (DIR) Post #9x3ShHUS12BEM5niwy by sir@cmpwn.com
       2020-07-13T20:51:08Z
       
       0 likes, 1 repeats
       
       @wolf480pl aye, and the extra UI indicating the CI job status