~brhiggins

United Kingdom

https://brhiggins.com


#348 SSH clone URL replaced with HTTPS URL when building public repository 9 months ago

Ticket created by ~brhiggins on ~sircmpwn/git.sr.ht

#Summary

When submitting a build manifest to builds.sr.ht for a public repository, if sources contains an SSH URL for the project's git.sr.ht upstream, it gets replaced by an HTTPS URL before cloning.

This has the knock-on impact of causing failure of any step that pushes to the upstream.

#Steps

  • Create public or unlisted repository
  • Create build manifest including SSH clone URL as the source
  • Provide a private SSH key secret
  • Execute the build

#Expected

  • The SSH URL is used to clone the project, authenticating with the SSH key

#Actual

  • The project is cloned using the public HTTPS URL

#Resources

#318 Secret upload journey doesn't error when no radio buttons clicked 10 months ago

Ticket created by ~brhiggins on ~sircmpwn/builds.sr.ht

#Summary

When trying to upload a secret via the 'Manage secrets' page of build.sr.ht, it's easy to complete the journey without ticking a radio button. No error message is displayed, and the page just reloads.

#Steps

#Expected

An error message appears telling me I need to tick the 'File' radio button.

#Actual

The page reloads with no error message.

#Comments

Clicking the 'File' radio button causes the file upload elements to appear, which I interpreted mean I intended to upload my secret as a file. Via IRC chat I learned that I need to paste and click the 'File' radio, but then ignore the file upload. I think this journey could be improved a little.