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

Better architect releases in rule engine #123

Open
azuline opened this issue May 6, 2024 · 0 comments
Open

Better architect releases in rule engine #123

azuline opened this issue May 6, 2024 · 0 comments

Comments

@azuline
Copy link
Owner

azuline commented May 6, 2024

The rule engine operates on tracks, but some metadata properties belong to releases. How can we unify releases and tracks?

Protocol: Some matchers only match entire releases; other matchers only match entire tracks. Running a release action on a track modifies its entire release.

This is almost what happens right now, except when we modify a release variable on single track, it only updates the entire release if it is the first track.

The rules engine could be rearchitected to take into account this distinction as well.

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

No branches or pull requests

1 participant