Composable actions for linting manifest PR
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reviewing the repository structure and the referenced semantic-pr-title implementation. Define separate action subfolders and determine how PR titles, manifest paths, filenames, and field ordering will be checked. Done means downstreams can reference a subfolder action by SHA and the listed linting rules are enforced.
Written by the indexing model from the issue text.
Description
New actions should be stored under a subfolder, so downstreams can use it composably by referring uses: ScoopInstall/GithubActions/<subfolder>@<sha1>
Lint PR title
The following conventions to be followed:
- https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md#for-scoop-buckets
- https://github.com/ScoopInstaller/Main/blob/master/.github/pull_request_template.md?plain=1#L21
<manifest-name[@version]|\(chore\)>: <General summary of the pull request>
- parenthetical portion
(*)can appear as part of the<manifest>section ONLY when the diff of one PR involves multiple manifests- parenthetical portion supports wildcard
(*)or specific chars e.g.app-name(-beta), where the symbol rules also apply to.
- parenthetical portion supports wildcard
Reference for similar implementation approaches: https://github.com/chawyehsu/actions/tree/main/semantic-pr-title
Other linting rules to consider
- A manifest MUST be placed in the
bucketsubfolder of the bucket repository- (OPTION) or the nested subfolder of
bucketfolder
- (OPTION) or the nested subfolder of
- The name of a manifest MUST use lowercase letters, numbers, dots (.) and hyphens (-) only, and MUST NOT start with hyphens (-) and dots (.), and MUST NOT end with dots (.)
- The fields in a manifest SHOULD follow the general order defined in https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md#for-scoop-buckets
- Dominant language
- PowerShell
- Stars
- 32
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from ScoopInstaller/GithubActions
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ScoopInstaller/GithubActions#98 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ScoopInstaller/GithubActions#89 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in ScoopInstaller/GithubActions
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
galaxyproject/iwc#1500 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ClockGU/clockwork-backend#169 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
compiler-explorer/ce-ci#28 ·
-
bug dependencies kind:fix priority: P3 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
shep-pm/shep#1318 · 1 comment ·
Maintainers usually reply within 1 day
-
Context/namespace resources fail in-cluster: "Invalid kube-config file. No configuration found."Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100