Adapt the 'cargo' plugin to make better use of the YAML Node API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python, yaml
- Domain
- build-system, tooling
Research direction
Start by locating the cargo plugin in the repository and reading the linked GitLab issue for the missing context about the YAML Node API. Compare the plugin's current YAML handling with the API guidance there; done means the cargo plugin has been adapted as specified and its existing tests still pass.
Written by the indexing model from the issue text.
Description
I have no idea what this means but there was issue open at https://gitlab.com/BuildStream/bst-plugins-experimental/-/issues/13
- Dominant language
- Python
- Stars
- 8
- Forks
- 16
- Avg merge
- 36m
- Merged PRs (30d)
- 2
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.
More from apache/buildstream-plugins
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
apache/buildstream-plugins#110 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
apache/buildstream-plugins#108 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in apache/buildstream-plugins
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100