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
Linux and Windows CI builds for Pull Requests for all project fail if the remote branch name contains a forward slash / because such characters are valid for branch names but not for the uploaded PR asset names. See the discussion in PR 214 of CoinUtils.
This could be fixes by replacing such characters in the name of the uploaded PR assets, or by leaving out the remote branch name from the PR asset name altogether.
Since we rarely create PRs from branches with names like feature/foo this is not a very common issue.
The text was updated successfully, but these errors were encountered:
I was originally thinking of a single PR containing all the issues that we can add to over time. Otherwise, it may get a bit difficult to see at a glance how many issues have accumulated. An alternative would be to create a label for Actions-related issues. This is not a bad idea, actually. What do you prefer?
Linux and Windows CI builds for Pull Requests for all project fail if the remote branch name contains a forward slash / because such characters are valid for branch names but not for the uploaded PR asset names. See the discussion in PR 214 of CoinUtils.
This could be fixes by replacing such characters in the name of the uploaded PR assets, or by leaving out the remote branch name from the PR asset name altogether.
Since we rarely create PRs from branches with names like feature/foo this is not a very common issue.
The text was updated successfully, but these errors were encountered: