Skip to content

Conversation

@fvanderflier
Copy link
Collaborator

What Changed?

Why?

Closes #(issue number)

Type of Change

  • πŸ› Bug fix (fixes an issue without breaking existing functionality)
  • ✨ New feature (adds new functionality without breaking existing features)
  • πŸ’₯ Breaking change (existing functionality will be affected)
  • πŸ“ Documentation update
  • πŸ”§ Maintenance (refactoring, dependencies, configuration)

How Did You Test This?

What I tested:

  • [ ]
  • [ ]

How to test it:

Review Checklist

  • My code follows the project's style and conventions
  • I've reviewed my own code for obvious issues
  • I've added comments where the code might be confusing
  • I've updated relevant documentation (if needed)
  • I've tested my changes and they work as expected

Screenshots / Additional Context

@fvanderflier fvanderflier force-pushed the feature/274-run-tests-in-pipelines branch from f4756fe to b3ce187 Compare January 28, 2026 14:32
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.

2 participants