← Back to issue list

Add TICS workflows

View original Github issue

Metadata

Project
starflow
Number
#21
Type
issue
State
closed
Author
lengau
Labels
Status: Triaged
Created
Updated
Closed

Current evaluation

Implemented via pull request #51, the scheduled TICS workflow replaces per-PR execution. The request was fulfilled and the issue closed.

Suggested action:

No scores available.

Issue body

Run TICS through a workflow that uses scheduling rather than running on every PR. https://github.com/canonical/starflow/pull/18/files#r1838397674

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Implemented via pull request #51, the scheduled TICS workflow replaces per-PR execution. The request was fulfilled and the issue closed.
qwen/qwen3.6-35b-a3b Implemented and merged in PR #51. The requested scheduled TICS workflow was added, replacing per-PR execution.
qwen/qwen3.6-35b-a3b Resolved by pull request #51, which implemented the requested scheduled TICS workflow instead of running it on every PR. Closed as superseded by this merge.
qwen3.6-35b-a3b-mtp-q6 Scheduled TICS workflows were implemented to replace per-PR execution. The request was fulfilled and merged in pull request #51 by @upils.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#35 feat: TICS workflow starflow closed Closed and superseded by pull request #51. The TICS workflow feature was replaced by an updated implementation in the referenced PR, leaving this request unmerged.
83%
#5319 ci: update tics workflow snapcraft closed Superseded by CRAFT-4322. The PR to fix a broken TICS CI workflow was closed without review or merge to redirect efforts to the referenced issue.
75%
#464 ci: update tics workflow fetch-service merged Merged after approval from two reviewers and successful CI checks. Updates the TICS CI workflow, modifying one file with two additions and seven deletions.
71%
#463 ci: update tics workflow fetch-service closed Updates to the tics CI workflow were closed without merging. A failing CI check halted progress, and with no reviewer activity, the changes were abandoned.
71%