Replace workflow with project automations#136831
Merged
Merged
Conversation
ezio-melotti
requested changes
Jul 23, 2025
Member
ezio-melotti
left a comment
There was a problem hiding this comment.
I/Ezio can add such automation for the remaining projects, the question is whether this can be done before we remove this workflow?
The removed workflow only affects 2 projects, so once the "auto-add workflow" is added to them, this PR can be merged.
Updating the other projects is easy enough, and can be done at any time (as long as the maintainers are happy without it).
Also note that there are limits on the number of auto-add workflows, even though it's not clear to me if these are per-project or cumulative. I'm also not sure if having multiple auto-add workflows rather than a single workflow (like the one being removed) uses more CI minutes and is therefore less preferable.
This comment was marked as resolved.
This comment was marked as resolved.
ezio-melotti
approved these changes
Jul 23, 2025
8 tasks
danigm
pushed a commit
to openSUSE-Python/cpython
that referenced
this pull request
Oct 7, 2025
Remove unnecessary workflow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of: python/core-workflow#467
As discussed with Ezio before on the linked issue:
This has been tested on the sqlite3 project (and corresponding label topic-sqlite3, an example of how it is run can be found on this issue) and the Docs PRs project (there are many examples of this one!) [Link not accessible to general public].
I/Ezio can add such automation for the remaining projects, the question is whether this can be done before we remove this workflow?
It would also make sense to add it to the several other cases of a project & relevant label apart from the two covered by the existing workflow, I am happy to do this:
topic-IDLE: IDLE Project
topic-ctypes: Ctypes project
topic-asyncio: Async IO project
topic-subinterpreters: subinterpreters project
topic-multiprocessing: multiprocessing project