Conversation
|
Something here seems off, as e.g. NixOS/nixpkgs#475599 or NixOS/nixpkgs#468036 was merged (added to the merge queue) by @zowoq |
|
Indeed, 120 merges to master in January, by my count. Certainly not inactive. |
|
The relevant portion of the run's log is at https://github.com/NixOS/nixpkgs-committers/actions/runs/21681495453/job/62516925152#step:5:872. I ran the same command myself (copying from https://github.com/NixOS/nixpkgs-committers/blob/main/scripts/retire.sh#L112 for proper escaping, and adding the Very strange that it seemingly returned 0 results before! |
Random flukes and weird behaviour are not that unusual for GitHub 🫣 I was initially wondering if this could be related to a change in behaviour, such as commit signature validation. Glad that you found the commands operating normally now. I think we can close this? |
@mdaniels5757 FYI the CI logs should work with copy paste to try the commands locally actually! |
This is an automated PR to retire @zowoq as a Nixpkgs committer because they have not used their commit access in the past year.
@zowoq: You can make a comment stating why you believe your commit access should be kept. Otherwise, this PR will be merged and implemented in one month.
Note
Commit access is not required for most forms of contributing, including being a maintainer and reviewing PRs. It is only needed for things that require
writepermissions to Nixpkgs, such as merging PRs.