workflows lint-config always fails on ClusterTriggerTemplate manifests ("found nothing to lint")

Open
#1,612 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
kubernetes
Domain
devops, tooling

Research direction

Start with the workflows lint-config entry point and the i15-1-trigger ClusterTriggerTemplate manifest, then reproduce the reported "found nothing to lint" failure. Trace how ClusterTriggerTemplate resources are selected for linting; done means this manifest is recognized and the lint workflow completes successfully.

Written by the indexing model from the issue text.

Description

Template Name: i15-1-trigger - Errors found:
found nothing to lint in the specified paths, failing...

This is a trigger template executed when a stop message is recieved, current this fails on lint, because it doesn't recognise a ClusterTriggerTemplate

Dominant language
Rust
Stars
7
Forks
6
Avg merge
1d 8h
Merged PRs (30d)
56

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DiamondLightSource/workflows

All issues in DiamondLightSource/workflows

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.