axodotdev / axodotdev/harbor

cleanup the workflow impls

Open
#11 0 comments 0 reactions 0 assignees View on GitHub
ci-scripts enhancement
Dominant language
JavaScript
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Description

https://github.com/axodotdev/cargo-vet-school/tree/main/.github/workflows

Now that I've learned github-script lets you do inline JS, we *can* just kill the `certify` dir which exists to create a single JS workflow. Of course this would lock the current impl *even more* into github but it's also not exactly *complex* logic. The challenge is mostly getting github to not freak out about permissions and to trigger in the right situations, which is necessarily domain-specific.

There's also just a bunch of commented out gunk from experiments and bad formatting/style.

Not sure how much of this stuff should be "published actions".

Not sure how much should be abstracted into a new rust cli (or made into builtin functionality of cargo-vet!).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the workflows under .github/workflows and the certify directory to map the current implementation and its commented experiments. Clarify whether the goal is a single inline-JavaScript workflow, published actions, or a Rust CLI, then define the intended permissions and trigger behavior as the completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
ci-cd
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.