rhobs / rhobs/observability-operator
Lint github actions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 90
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 22
Description
We have a github actions linter in place and it runs on PRs. Since this worklflow was added after the initial actions were committed I think a large portion of our action was never run through the linter.
We should probably do that. Found via https://github.com/rhobs/observability-operator/pull/231#issuecomment-1337274347
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing GitHub Actions workflows and the linter invocation added for pull requests, using the linked pull request comment for context. Run the linter against the earlier workflows and address the findings until the complete set of actions passes linting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100