spec-generator sometimes generates issue tracking links pointing here instead of at the spec's repo #821

Activity

1. deniak

   assigned

   kfranqueiro

   on Oct 8, 2026
2. kfranqueiro commented on Oct 8, 2026

   

   kfranqueiro

   on Oct 8, 2026

   Last edited by kfranqueiro

   Contributor

   More actions

   This is evidently caused by the following combination, specifically when uploading a file to process with Bikeshed:

   • In the absence of explicit repository metadata, Bikeshed defaults to checking for an origin remote
   • The spec-generator server runs from a git checkout of spec-generator, and stores temporary files in a subfolder of the checkout

   This results in Bikeshed thinking that Repository should default to the spec-generator repo. Note that using a URL rather than file upload, or uploading a tarball rather than an individual file, does not produce this behavior; instead, Repository is not set at all.

   I have always found it odd that spec-generator stores uploads and crawled files in a subfolder rather than in the OS temp directory, so I've opened PR #822 to address that, which will also resolve this.

   Note, however, that this fix will still not result in Repository pointing to the webrtc-diagnostic-logging repo; instead it will not point to any repo, consistent with current behavior when specifying a URL. The best options to resolve that would be to either define Repository explicitly, or run bikeshed locally on the file within the repo checkout. (Bikeshed can also be installed within a GitHub workflow.)
3. kfranqueiro

   closed this as completedin #822on Oct 13, 2026