automate adding Container labels

Open
#93 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, tooling

Research direction

No repository files are named. Start with the linked GitHub Actions label-workflow documentation and inspect existing workflows and label configuration in this repository, then confirm how CSPO and csctl are in scope. Done means relevant pull requests, Renovate pull requests, and issues receive the Container label through an agreed automation approach.

Written by the indexing model from the issue text.

Description

Container

From what I understand, I think we need Container label on this repo, CSPO and csctl.

pull request

I think we can automate it for pull requests using actions/labeler and for renovate PRs, we can use renovate itself.

issues

For issues, I think we can use the following:
https://docs.github.com/en/actions/managing-issues-and-pull-requests/adding-labels-to-issues#creating-the-workflow

This runs on every issue open and reopen which might be too much to we will never notice it, Given it runs in ground. If it sounds too much then we can use a cron workflow for the same.

/kind feature

// cc @janiskemper @jschoone

Dominant language
Go
Stars
18
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 SovereignCloudStack/cluster-stack-operator

All issues in SovereignCloudStack/cluster-stack-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.