- Notifications
You must be signed in to change notification settings - Fork6
Roadmap
Astrid Avalin Soerensen edited this pageMay 12, 2025 ·5 revisions
This document tracks the major features and improvements we aim to deliver for the Unity-CI-Templates project.
Want to suggest something or help contribute? Please open aDiscussion or anIssue.
- Modular CI/CD pipeline for Unity projects
- Supports preview, release candidate, and release builds
- Automated Unity testing (edit mode, play mode)
- GitHub Releases integration
- Deploy to GitHub Pages, itch.io, Firebase, S3, Steam, and more
- Discord + Slack notifications
| Feature | Status | Notes |
|---|---|---|
| Migrate YAML workflows to reusable actions | Ongoing | Gradually replace inline YAML with composite actions for better modularity and DRY code |
| Support self-hosted runners | Planned | Allow workflows to run on user-provided runners |
| Force combined artifact mode | Planned | Add option to enforce combined artifacts even if not strictly required |
| Quiet Mode implementation | Planned | Suppress verbose logs in entire CI/CD runs |
| Add Microsoft Teams notifications | Planned | Extend notify step to support Teams |
| Support more build target platforms | Planned | Example: UWP, Oculus, Microsoft HoloLens |
| Support more deploy target platforms | Planned | Example: AppCenter, Google Play, TestFlight |
| Verify Build Profiles | Planned | Ensure the selected Unity Build Profiles are properly applied during CI builds |
- Template wizard or setup generator
- GitHub App integration (instead of pure Actions)
- Visual status dashboard (per-project deploy + release status)
We welcome your help!
If you want to tackle one of these features, please:
- Check for an open Issue or create one.
- Comment or open a Discussion to signal interest.
- Follow the contribution guidelines.
Let’s build better Unity pipelines together! 🚀
Need help? Join theDiscussions or open anIssue.