Skip to content

chore: sort & add contributor#379

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
automated-updates-378
Closed

chore: sort & add contributor#379
github-actions[bot] wants to merge 1 commit into
mainfrom
automated-updates-378

Conversation

@github-actions

Copy link
Copy Markdown

Automated workflow update

Changes include:
- Sorted conferences
- Added contributor

Please review and merge these automated updates.

@JesperDramsch

Copy link
Copy Markdown
Owner

Closing — product of the broken all-contributors bot. This PR strips @JesperDramsch's contributions from 17 types down to just conference in .all-contributorsrc, README.md and CONTRIBUTING.md (the known all-contributors-cli array-replacement behaviour). No conference data is lost: every entry here (PyCon US 2026 archival + camp-conference re-sort) is already on main and was carried by #376. The pr-sort workflow is being fixed to drop the unconditional all-contributors add that defeats the existing guard.

@JesperDramsch JesperDramsch deleted the automated-updates-378 branch June 27, 2026 20:42
JesperDramsch added a commit that referenced this pull request Jun 27, 2026
The pr-sort workflow ran an unconditional `all-contributors add <user>
conference` before the jq guard meant to prevent re-adding an existing
contribution type. all-contributors-cli replaces a contributor's entire
contributions array when re-adding a type they already have, so the
unconditional call collapsed contributors (e.g. JesperDramsch: 17 types ->
["conference"]) on every run. The guard then read the already-stripped
file, found "conference" present, and skipped the second add — silently
defeating the fix.

Remove the unconditional add so the jq guard is the only add path: skip
when the contributor already has "conference", add only for genuinely new
contributors. Fixes the corruption behind the closed PRs #371 and #379.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant