!sBfrWMVsLoSyFTCkNv:nixos.org

OfBorg

181 Members
Number of builds and evals in queue: <TBD>63 Servers

Load older messages


SenderMessageTime
22 May 2021
@hexa:lossy.networkhexa joined the room.17:22:59
@7c6f434c:nitro.chat7c6f434c joined the room.17:25:13
@colemickens:matrix.orgcolemickens joined the room.17:26:40
@qyliss:fairydust.spaceAlyssa Ross joined the room.18:01:56
@andi:kack.itandi-Another week another attempt at getting the GitHub Actions CI to pass on my PR..21:40:08
@andi:kack.itandi-Still failing on the same weird issue.21:48:04
23 May 2021
@lukegb:zxcvbnm.ninjalukegb (he/him) joined the room.00:34:07
@lukegb:zxcvbnm.ninjalukegb (he/him) changed their display name from lukegb to lukegb (he/him).01:33:10
@sumner:sumnerevans.comsumner joined the room.04:51:57
@v:anomalous.euV joined the room.11:36:33
@grahamc:nixos.org@grahamc:nixos.orgwe should probably move back some of the thinsg ofborg already does to ofborg12:37:42
@grahamc:nixos.org@grahamc:nixos.orglike labels12:37:43
@andi:kack.itandi-Is that on the back of the API rate limit (rather than in principle it should be ofborg doing it)?12:40:51
@sandro:supersandro.deSandro 🐧
In reply to @grahamc:nixos.org
like labels
Then you need to deploy it everytime something is changed
12:49:35
@sandro:supersandro.deSandro 🐧On the other hand actions have regularly problems and issues12:50:28
@grahamc:nixos.org@grahamc:nixos.orgAPI rate limit, I don't feel very precious about the code in ofborg12:52:18
@grahamc:nixos.org@grahamc:nixos.orgalso I'd be happy to expand merge and deployment rights12:52:36
@grahamc:nixos.org@grahamc:nixos.orggotta run, I'm doing airport stuff today, so I'll be afk for several hours12:53:20
@andi:kack.itandi-More features into ofborg would really be nice. There was some discussion a out code owners recently. You can't use groups right now as the group requires write access to be mentioned. This would be something ofborg could do as well. It would allow maintainers to be pinged without them having commit access.12:54:19
@sandro:supersandro.deSandro 🐧If it would require a redeploy for every change it would be a hassle12:56:00
@andi:kack.itandi-It depends on the kind of change. For the code owners example it should be based off the repo checkout and not some config file.12:57:28
@lukegb:zxcvbnm.ninjalukegb (he/him)Right, there's no reason that parts of the ofborg config couldn't be in the main nixpkgs repo13:36:33
@lukegb:zxcvbnm.ninjalukegb (he/him)especially if it's just a json file read off master13:36:42
@andi:kack.itandi-I was more thinking about implementing the same codeowner format that GitHub already users13:42:29
@andi:kack.itandi-That would allow us to overcome the shortcomings of GitHubs implementation while only maintaining one file.13:42:51
@andi:kack.itandi-I know that @piegames:matrix.org has run into that issue lately.13:43:51
@andi:kack.itandi-(now would be a nice time to throw an invite to the channel to that person...)13:44:10
@sandro:supersandro.deSandro 🐧https://matrix.to/#/#ofborg:nixos.org13:45:20
@cole-h:matrix.orgcole-hRedeploying for every change isn't really a hassle ;) That said, I think using the tag config inside Nixpkgs itself is a good idea.16:05:29
@qyliss:fairydust.spaceAlyssa RossI had a WIP branch for that16:06:22

Show newer messages


Back to Room ListRoom Version: 6