Skip to content

Refactor workflow service boundaries#86

Open
YunaBraska wants to merge 1 commit into
workflow-internals-basefrom
refactor-service-boundaries
Open

Refactor workflow service boundaries#86
YunaBraska wants to merge 1 commit into
workflow-internals-basefrom
refactor-service-boundaries

Conversation

@YunaBraska
Copy link
Copy Markdown
Owner

@YunaBraska YunaBraska commented May 24, 2026

Summary

  • stack the service-boundary refactor on top of Refactor workflow internals base #90 instead of conflicting with dev
  • collapse the split client/entry/git/run/settings/state/syntax internals into fewer Workflow* service entry points
  • keep the newer release/dependency docs and Gitea workflow icon behavior from the base layer

Why

This is the second layer of the refactor stack. #90 parks the accidental dev work cleanly; this PR keeps the useful older service-boundary idea without undoing the fresh base changes. The branch was backed up before rewriting. Paper trail intact, chaos contained.

Checks

  • ./gradlew --no-daemon compileJava compileTestJava --warning-mode all
  • ./gradlew --no-daemon test --warning-mode all
  • ./gradlew --no-daemon check verifyPlugin buildPlugin --warning-mode all

@YunaBraska YunaBraska changed the base branch from dev to workflow-internals-base June 8, 2026 09:08
@YunaBraska YunaBraska force-pushed the refactor-service-boundaries branch from 971bdf0 to 30cdebb Compare June 8, 2026 09:19
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

Successfully merging this pull request may close these issues.

1 participant