Add support for new rpm-content-package filters
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the referenced pulp_rpm pull request, especially its changed files and filter details. Then locate the corresponding filter handling in pulp-cli and determine the command behavior and tests that must reflect the new filters. Done means pulp-cli supports the filters described by that pull request and the relevant tests pass.
Written by the indexing model from the issue text.
Description
Summary
See https://github.com/pulp/pulp_rpm/pull/3137/files for details
- Dominant language
- Python
- Stars
- 43
- Forks
- 52
- Avg merge
- 11h 38m
- Merged PRs (30d)
- 11
Contributor 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 pulp/pulp-cli
-
bug Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
easy fix feature request
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
bug Triage-Needed
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·