| 19 May 2025 |
 Winter | definitely not in the squash merges i’ve seen | 19:25:46 |
 FliegendeWurst | maybe it depends on the repository settings | 19:26:27 |
| FliegendeWurst | But it has to be a squash merge. The merged commit has only one parent | 19:26:41 |
 danth | In reply to @winter:catgirl.cloud
i didn’t think squash merges had the “Merge pull
request …” prefix? There's an option to change the default message in the repository settings, although none of these sound like that specific format | 19:35:58 |
| danth | Redacted or Malformed Event | 19:36:07 |
| danth | (forgot we can't send screenshots here, but hopefully u get the idea) | 19:36:48 |
 emily | pretty sure that's not a thing | 21:42:54 |
| emily | not sure what happened there – I suspect manually editing the title of a squash merge | 21:43:16 |
| 20 May 2025 |
 Ihar Hrachyshka | Redacted or Malformed Event | 01:08:12 |
| Ihar Hrachyshka | * from nixpkgs manual: "A more formal definition of the platform support tiers is provided in RFC046, but has not been fully implemented yet."
wonder if this should be "fully implemented" for the sake better standing of aarch64-darwin in the eyes of packagers that don't care; and what it would take to make the official tier list a reality (the one in RFC046 is wildly out of date)
ah should have just searched through PRs!.. I guess it's: https://github.com/NixOS/nixpkgs/pull/401821 | 01:09:09 |
| Ihar Hrachyshka | * ~~from nixpkgs manual: "A more formal definition of the platform support tiers is provided in RFC046, but has not been fully implemented yet."~~
~~wonder if this should be "fully implemented" for the sake better standing of aarch64-darwin in the eyes of packagers that don't care; and what it would take to make the official tier list a reality (the one in RFC046 is wildly out of date)~~
ah should have just searched through PRs!.. I guess it's: https://github.com/NixOS/nixpkgs/pull/401821 | 01:09:22 |
| Ihar Hrachyshka | * from nixpkgs manual: "A more formal definition of the platform support tiers is provided in RFC046, but has not been fully implemented yet."
wonder if this should be "fully implemented" for the sake better standing of aarch64-darwin in the eyes of packagers that don't care; and what it would take to make the official tier list a reality (the one in RFC046 is wildly out of date)
ah should have just searched through PRs!.. I guess it's: https://github.com/NixOS/nixpkgs/pull/401821
| 01:09:33 |
| Winter | In reply to @emilazy:matrix.org
not sure what happened there – I suspect manually editing the title of a squash merge probably | 01:53:22 |
| Winter | you’d just think squash merges would properly set committer nonetheless | 01:53:56 |
|  Gwenn Le Bihan joined the room. | 08:12:55 |
 Grimmauld (any/all) | Or at least Co-author field if done in github... | 09:45:52 |
|  kongrooparadox joined the room. | 21:45:30 |
| 21 May 2025 |
|  WeetHet changed their profile picture. | 10:59:08 |
|  sinan changed their profile picture. | 11:59:58 |
| sinan changed their profile picture. | 12:00:45 |
|  oddlama changed their display name from Malte to oddlama. | 17:42:01 |
|  @alanpearce:private.coffee left the room. | 19:05:02 |
|  @bloxx12:matrix.org left the room. | 21:30:09 |
| 22 May 2025 |
|  Perchun Pak [don't ping; dm instead] changed their display name from Perchun Pak to Perchun Pak [don't ping; dm instead]. | 13:50:43 |
| emily | Darwin builder is load avg ~19 (~6 of that is my fault though) | 13:53:52 |
 Matt Sturgeon | In Nixvim we've been using @glepage:matrix.org's PAT for pushing lockfile update PRs, because you need to push as a "real" user to trigger CI.
This gets a bit confusing sometimes, so we'd like to push those PRs as @nix-infra-bot instead. Would it be possible to add a Personal Access Token to our repo secrets, so we can have our CI use that token instead?
It would need write access to Nixvim, and ideally the secret would be named something like INFRA_BOT_TOKEN. | 22:31:09 |
| danth | FYI you can also install a GitHub app on the repo and use `actions/create-github-app-token` | 23:12:58 |
| danth | * FYI you can also install a GitHub app on the repo and use actions/create-github-app-token | 23:13:37 |
| Matt Sturgeon | I'm unfamiliar, would that create a token for doing things as the "app"?
I feel like that'd count as doing things "as a bot" and therefore still wouldn't trigger on:push workflows.
If it does trigger workflows on PRs pushed to by this app token, then that may be neater.
Is this what you do in Stylix for updating your lockfile? | 23:17:33 |
| danth | Yeah, it can trigger workflows like normal, and everything it does shows up as the bot user (example here.It's also a bit more secure since you can fine tune permissions on the app and the generated tokens only last for 1 hour | 23:27:18 |
