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

Separate Git branch references from the Workflow concept #164

Open
MarkRobbo opened this issue Aug 23, 2017 · 0 comments
Open

Separate Git branch references from the Workflow concept #164

MarkRobbo opened this issue Aug 23, 2017 · 0 comments

Comments

@MarkRobbo
Copy link
Member

MarkRobbo commented Aug 23, 2017

Currently workflows can be added by branch (eg master) or commit ID (eg aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d). These are added as distinct workflows even if they refer to the same thing at a moment of time.

This is due to the GitDetails object used as the retrievedFrom ID of the workflow being a combination of the repository URL, branch (or commit ID), path and packed ID.

Ideally the concept of a branch reference or tag would be a higher level layered concept which points to a commit ID similar to the Git internals, so that if a branch leaves a commit behind, it still exists in the database and permalinks will continue to exist.

For now, the workaround to this will be to create an additional workflow for the commit ID when a branch moves on

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