Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconsider output branch naming #28

Open
ronald-jaepel opened this issue Nov 28, 2023 · 0 comments
Open

Reconsider output branch naming #28

ronald-jaepel opened this issue Nov 28, 2023 · 0 comments

Comments

@ronald-jaepel
Copy link
Contributor

In GitLab by @r.jaepel on Nov 28, 2023, 11:32

From @j.schmoelder : I think we could also reconsider the naming convention of the output branches. While unlikely, a key collision is theoretically possible if two runs are started at the same time (see also #24). Instead, we could either simply use a unique ID (ideally s.t. we can use a long and a short format for referencing, just like for commit hashes) or if we go for some kind of queuing system, all runs must consecutive anyway, so we could simply give them an increasing counter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant