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
Is there any reason you don't use a hash or anything to practically guarantee collisions altogether?
For instance, if you pulled the branch's latest commit, you could take that commit's hash's first 7 digits and integrate it into the alias, similar to how non-aliased now deploys get named package-name-hashgoeshere.now.sh.
If you did this, the structure could be {user-name}-{repo-name}-{branch-name}-{commit-hash}. Granted this may be too long at this point, so you might consider cutting out the branch-name since that's now redundant, I think
The current alias structure is of the form:
{repo-name}-{my-branch}
.I think we should add the repo owner to the alias, for example:
zpnk-hello-world-some-changes
.This will prevent collisions on project forks, etc.
The text was updated successfully, but these errors were encountered: