!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

466 Members
Declarative Home Automation and other Sidequests | https://wiki.nixos.org/wiki/Home_Assistant132 Servers

Load older messages


SenderMessageTime
30 Mar 2025
@continous:matrix.orgcontinous hexa: I'm a bit confused, should I use the normal pull request template or no? I make a single line change to home-assistant's components nix file 01:26:18
@continous:matrix.orgcontinousAlso add myself to maintainers01:26:28
@continous:matrix.orgcontinousSee: https://github.com/NixOS/nixpkgs/compare/master...Continous:nixpkgs:decora-wifi01:27:02
@hexa:lossy.networkhexathree commits01:27:26
@hexa:lossy.networkhexa
  • maintainers: add continous
  • python313Packages.decora-wifi: init at $version
  • home-assistant: update component-packages
01:27:55
@continous:matrix.orgcontinousSo I should submit each separately?01:28:12
@hexa:lossy.networkhexa the last commit needs to be generated by running ./pkgs/server/home-assistant/update-component-packages.py 01:28:17
@hexa:lossy.networkhexaone PR, three commits01:28:21
@continous:matrix.orgcontinousSo the last commit I should ommit, or run update-component-packages.py and commit the output?01:29:09
@continous:matrix.orgcontinous* So the last commit I should ommit, or run ``update-component-packages.py and commit the output?01:29:24
@continous:matrix.orgcontinous* So the last commit I should ommit, or run update-component-packages.py and commit the output?01:29:33
@hexa:lossy.networkhexarun the script and commit the result with the commit message as above01:29:39
@continous:matrix.orgcontinousOk.01:30:41
@continous:matrix.orgcontinousI sent it boys https://github.com/NixOS/nixpkgs/pull/39456009:36:39
@k900:0upti.meK900Added a few comments09:42:04
@k900:0upti.meK900Feel free to ask here if you have questions09:42:15
@continous:matrix.orgcontinousI am still cleaning up a bit, basically.09:48:53
@k900:0upti.meK900Sure, there's no rush09:49:28
@continous:matrix.orgcontinousHow...or what even...is squashing commits?09:49:34
@k900:0upti.meK900Well there's a bunch of tools that can do it09:49:55
@k900:0upti.meK900Fundamentally what you want to do is have a clean commit history09:50:44
@k900:0upti.meK900It's a different way of thinking about what your commits represent, I guess?09:51:46
@k900:0upti.meK900I'm sorry if I'm getting too philosophical about it09:51:54
@k900:0upti.meK900But the idea is that instead of recording a log of your work, in a big project you want to break down your changes into a stack of patches that build on top of each other09:52:31
@k900:0upti.meK900And every patch does one thing, or at least as close to one thing as possible09:52:45
@k900:0upti.meK900In your case, it would be something like 1) add yourself to maintainer list 2) add the new package with you as maintainer 3) regenerate HA components09:53:10
@continous:matrix.orgcontinousDon't worry lol. I've literally never used git before so this is me being entirely fresh to proper "programming"09:54:18
@k900:0upti.meK900Yeah so basically there's kind of two approaches to git09:54:41
@continous:matrix.orgcontinousI just don't really know how to remove commits.09:54:45
@k900:0upti.meK900One is what you're doing, which is keeping an actual history of the work09:54:49

Show newer messages


Back to Room ListRoom Version: 6