-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
sesh: 2.16.0 -> 2.17.1, add randomdude to maintainers list #430134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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
Should I squash the commits? |
Regroup the edits: maintainer entry first, then new package. Just two commits. And also look up how to name the commits |
7c4c5e2
to
a8d5638
Compare
I've done that, is it good to go? (After gwg313 reviews it of course) |
Ah, I mistook the contents of your PR. There should be 3 (the following are not title examples, unless quoted):
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) |
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 |
a8d5638
to
3258c74
Compare
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. |
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. |
Don't worry about combining our work, the version fix has been merged now |
Sorry for the inconvenience, My machine is up and running how, how should I approach resolving the conflicts? (Specifically naming the commits) |
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. |
a32ae8d
to
0797d48
Compare
0797d48
to
38f0736
Compare
Thanks a lot for all of your patience! I've fixed the conflicts now and the PR is ready for review. |
|
name = "Random Dude"; | ||
email = "randomdude16671@proton.me"; | ||
github = "randomdude16671"; | ||
githubId = 210965013; |
There was a problem hiding this comment.
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
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
passthru.tests
.nixpkgs-review
on this PR. See nixpkgs-review usage../result/bin/
.