Skip to content

Add OR alternatives to label select#7753

Closed
viraatdas wants to merge 1 commit into
pulp:mainfrom
viraatdas:libra/7435-label-select-or
Closed

Add OR alternatives to label select#7753
viraatdas wants to merge 1 commit into
pulp:mainfrom
viraatdas:libra/7435-label-select-or

Conversation

@viraatdas
Copy link
Copy Markdown

Summary

  • add pipe-separated OR alternatives within pulp_label_select terms
  • keep comma-separated terms as AND
  • document the new label filter syntax and add functional coverage

Refs #7435

Verification

  • uvx ruff check pulpcore/app/viewsets/custom_filters.py pulp_file/tests/functional/api/test_labels.py
  • /Users/viraat/.local/share/uv/python/cpython-3.11-macos-aarch64-none/bin/python3.11 -m compileall pulpcore/app/viewsets/custom_filters.py
  • git diff --check

I also attempted uv run --python 3.11 --with pytest --with pytest-django --with-editable . pytest pulp_file/tests/functional/api/test_labels.py -k test_label_select -q, but this local checkout cannot collect functional tests because generated pulpcore.client bindings are not present.

AI Usage

Generated by Libra Issues / Codex and reviewed before submission.

Refs pulp#7435

AI Usage: Generated by Libra Issues / Codex, reviewed and tested by Viraat Das.
@gerrod3
Copy link
Copy Markdown
Contributor

gerrod3 commented May 29, 2026

@viraatdas Unrelated to the code, can you explain what "Libra Issues" is? I did a google search and didn't find anything but astrology 🤣.

@viraatdas
Copy link
Copy Markdown
Author

Closing this duplicate because the contribution has been republished from the Libra Issues machine user: #7755

@viraatdas viraatdas closed this May 29, 2026
@viraatdas
Copy link
Copy Markdown
Author

viraatdas commented May 29, 2026

Hey @gerrod3. I am building Libra Issues and have reached a level where I feel comfortable allowing it to make PRs on my behalf are trying it out in AI-friendly repositories :D

@gerrod3
Copy link
Copy Markdown
Contributor

gerrod3 commented May 30, 2026

@viraatdas Interesting... Do you have a blog or forum with some more info or FAQ? I would like to know some more about yours and the agent's process for handling interactions with actual human maintainers. Here's some basic Qs:

  1. How does a repository opt out if they decide they don't want autonomous agent fly-by PRs? Reading your site I assume a human has to trigger the bot, but what prevents a community user from triggering it for every issue?
  2. How does the agent handle feedback on the PR? If we close the PR will the agent try again?
  3. Is there any logging for the agent run? What it did, who/what started it? Is there anyway to trace the provenance of the work? Being able to find a human that is accountable for the actions of agent is really important.

I'll note that we haven't been inundated with contributions from agents like some big open-source repos have been, but if this is the start of that then we might have to become more restrictive on who is allowed to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants