Skip to content

Conversation

randomdude16671
Copy link
Contributor

sesh update

Updated the version of the sesh terminal session manager.
from: 2.16.0 -> 2.17.1
(this is my first contribution to nixpkgs, I apologize for any errors)

Maintainers update

Added myself to the list of maintainers of sesh as I am willing to maintain package, the original maintainer (@gwg313) is still included in the list.

Things done

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. 12.first-time contribution This PR is the author's first one; please be gentle! 8.has: maintainer-list (update) This PR changes `maintainers/maintainer-list.nix` labels Aug 1, 2025
@nix-owners nix-owners bot requested a review from gwg313 August 1, 2025 14:10
Copy link
Contributor

@acid-bong acid-bong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi and welcome to Nixpkgs. Please, read the docs linked in the last checklist item. They'll tell you how to organize your commits

@randomdude16671
Copy link
Contributor Author

Should I squash the commits?

@acid-bong
Copy link
Contributor

Regroup the edits: maintainer entry first, then new package. Just two commits. And also look up how to name the commits

@Sigmanificient Sigmanificient changed the title Add self to maintainers list, update sesh sesh: 2.16.0 -> 2.17.1, add randomdude to maintainers list Aug 4, 2025
@randomdude16671
Copy link
Contributor Author

I've done that, is it good to go? (After gwg313 reviews it of course)

@acid-bong
Copy link
Contributor

Ah, I mistook the contents of your PR. There should be 3 (the following are not title examples, unless quoted):

  • version bump
  • "maintainers: add randomdude"
  • "sesh: add randomdude as maintainer"

Sorry for confusion

@randomdude16671
Copy link
Contributor Author

Ah, I mistook the contents of your PR. There should be 3 (the following are not title examples, unless quoted):

  • version bump
  • "maintainers: add randomdude"
  • "sesh: add randomdude as maintainer"

Sorry for confusion

Sure, that's no problem. Shall I delete this PR and send another one with the required commit structure? (I'm not that experienced with Git, if there's an other way please do tell me)

@acid-bong
Copy link
Contributor

No need to close:

# 2, because you have 2 commits currently
# and mixed reset (default value) to keep your changes intact
git reset HEAD~2

git commit maintainers -m "maintainers: add randomdude"

# here you interactively choose the maintainers line (git will provide the instructions)
git commit -p pkgs -m "sesh: add randomdude to maintainers"

# and commit the rest, which is version bump + new hashes
git commit pkgs -m "sesh: 2.16.0 -> 2.17.1"

# and finally you force-push the branch here
git push --force-with-lease

@t-monaghan
Copy link
Member

t-monaghan commented Aug 8, 2025

From a review suggestion from @acid-bong I've combined the work here into my PR #431945

Looks like me cherry-picking this work isn't possible due to difficulties with the commit verification. I'll try find another approach.

@randomdude16671 I'm happy for you to cherry pick my commits onto this PR if that works for you.

@randomdude16671
Copy link
Contributor Author

I don't think I can do that very quickly, my machine is currently under service and it needs time, I'll inform you for any updates about the condition.

@t-monaghan
Copy link
Member

Don't worry about combining our work, the version fix has been merged now

@nixpkgs-ci nixpkgs-ci bot added the 2.status: merge conflict This PR has merge conflicts with the target branch label Aug 23, 2025
@randomdude16671
Copy link
Contributor Author

randomdude16671 commented Aug 23, 2025

Sorry for the inconvenience, My machine is up and running how, how should I approach resolving the conflicts? (Specifically naming the commits)

@t-monaghan
Copy link
Member

There should only be the three commits you have now, it would be best to create commits resolving any conflicts and squash/fixup them into the appropriate existing commit. e.g the conflict in sesh's maintainers list should be fixed, committed and then squashed into your second commit.

@randomdude16671 randomdude16671 force-pushed the sesh-update branch 2 times, most recently from a32ae8d to 0797d48 Compare August 26, 2025 14:16
@nixpkgs-ci nixpkgs-ci bot removed the 2.status: merge conflict This PR has merge conflicts with the target branch label Aug 26, 2025
@nix-owners nix-owners bot requested review from philiptaron and t-monaghan August 26, 2025 14:34
@randomdude16671
Copy link
Contributor Author

Thanks a lot for all of your patience! I've fixed the conflicts now and the PR is ready for review.

@philiptaron
Copy link
Contributor

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 430134
Commit: 38f0736da7c8ded304a82bbb36bb12783ed2db66


aarch64-darwin

✅ 1 package built:
  • sesh

name = "Random Dude";
email = "randomdude16671@proton.me";
github = "randomdude16671";
githubId = 210965013;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validated that this is @randomdude16671

@philiptaron philiptaron merged commit 8df3205 into NixOS:master Aug 26, 2025
25 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.has: maintainer-list (update) This PR changes `maintainers/maintainer-list.nix` 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. 12.first-time contribution This PR is the author's first one; please be gentle!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants