pulp / pulp/pulpcore

Make pulp_file issues discoverable separately from pulpcore issues.

Open
#5,487 1 comment 0 reactions 1 assignee View on GitHub

@gerrod3 is already working on this.

Since Aug 9, 2024.

file Task
Dominant language
Python
Stars
598
Forks
168
Avg merge
1d 4h
Merged PRs (30d)
86

Description

There may be other integrated plugins in the pulpcore source repo that are also affected.

Since pulp_file got merged into pulpcore it is hard to search either the issues or changelog for just pulp_file. And since there are far more pulpcore issues, this makes it hard to discover pulp_file issues at all.

The first idea is to add tags to issues in the pulpcore repo for each sub-component (core, file, etc.) this would make it easy to filter.

I am not sure if there is a better way, or how easy this would be to automate.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.