You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Thank you for this wonderful tool!
I have found, that branch names that contain / character don't pass format check when entered in the entry box on the nightly.link website.
A workaround is to replace / with e.g. -, and then, after clicking "Get Link", replace back the appropriate character directly in the address bar of the browser.
EDIT: the workaround doesn't seem to actually work, I can't get artifacts from a branch that has a space in it. Example: https://nightly.link/dyfer/supercollider/workflows/actions/topic/macos-legacy-fixes-rebased
The text was updated successfully, but these errors were encountered:
Thanks for the report. The pattern will be recognized in the input correctly now. And the branch with slash was already possible to use but the slash needs to be escaped as such:
Thank you for looking into this!
I understand that GitHub still reports wrong information. Do you know in what circumstances this happens? Is it due to dashes in the branch name?
Hello,
Thank you for this wonderful tool!
I have found, that branch names that contain
/
character don't pass format check when entered in the entry box on the nightly.link website.A workaround is to replace
/
with e.g.-
, and then, after clicking "Get Link", replace back the appropriate character directly in the address bar of the browser.EDIT: the workaround doesn't seem to actually work, I can't get artifacts from a branch that has a space in it. Example: https://nightly.link/dyfer/supercollider/workflows/actions/topic/macos-legacy-fixes-rebased
The text was updated successfully, but these errors were encountered: