Skip to content
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

chore: modernize PR template #92612

Closed
wants to merge 17 commits into from
Closed

chore: modernize PR template #92612

wants to merge 17 commits into from

Conversation

blaggacao
Copy link
Contributor

Also add links to marvin labels.
@Mic92 This is an intention-aware refactoring/strip down according to your nix-review package.

I also referenced @timokau 's marvin labels. They are unstable, so we should remember I put them here.

Follow up of #92244

Also add links to <experimental> marvin labels.
Copy link
Contributor Author

@blaggacao blaggacao left a comment

Choose a reason for hiding this comment

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

Some doubts ...

.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
- [ ] Ensured that relevant documentation is up to date
- [ ] other Linux (Ubuntu, Archlinux, Alpine, etc.). Please specify: ...

- [ ] If available*: tested via one or more NixOS test(s) `GITHUB_TOKEN=<YOUR_TOKEN> nixpkgs-review pr -p nixosTests.<test> <package> <pr-number>` (look inside [nixos/tests](https://github.com/NixOS/nixpkgs/blob/master/nixos/tests)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is this <test> <package> or more precisely rather <package> <package>? The usage example was ambiguous.

.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
- [ ] Tested sucessful built of final PR `GITHUB_TOKEN=<YOUR_TOKEN> nixpkgs-review pr <pr-number>`.
If suceeded, within the resulting `nix-shell`:
- [ ] Manually tested execution of all binary files (in `./results/bin/`)
- [ ] Include the manual checks and validations you did at the end in `editor ./report.md`
Copy link
Contributor Author

Choose a reason for hiding this comment

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

David Arnold added 2 commits July 7, 2020 15:17
`editor ./report.md` fits the bill
Requirements:
- install `nixpkgs-review` for good with `nix-env -f '<nixpkgs>' -iA nixpkgs-review`
- consult usage documentation: https://github.com/Mic92/nixpkgs-review#usage
- setup github api token: https://github.com/Mic92/nixpkgs-review#github-api-token
Copy link
Member

Choose a reason for hiding this comment

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

I think we can skip this step. The github token is only required for advanced features.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have a split argument about this:

  • pull requester will be nudged into graduating into reviewers
  • it helps towards a standardized review process if the pull requester already does: nixpkgs-review post-result

(and also: don't be too easy on pull requester, to shift the balance away from reviewers)

What do you think about those arguments?

Copy link
Contributor

@jtojnar jtojnar Jul 7, 2020

Choose a reason for hiding this comment

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

Could we make the request for API token part of first-time running nixpkgs-review/using the advanced features? That way we would not have to mention it here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jtojnar This is a really nice suggestion! I'll take it out here and open an issue to track it.

Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
@blaggacao blaggacao requested a review from Mic92 July 7, 2020 20:25
@nixos-discourse
Copy link

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/making-the-pull-request-template-more-beginner-friendly-nixpkgs/388/5

Copy link
Contributor

@jtojnar jtojnar left a comment

Choose a reason for hiding this comment

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

Nice. I like the simplification and having a single tool do as much as work possible will make reviewing much easier.

Only serious issue is making the local eval mandatory. Sure, nixpkgs-preview can take eval results from ofborg but that is not available before PR is opened and even a while after. Not sure if the local eval is even necessary, maybe we could just disable it, ofborg will eval it either way.

.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
- setup github api token: https://github.com/Mic92/nixpkgs-review#github-api-token
-->

- [ ] Tested sucessful build of final PR `GITHUB_TOKEN=<YOUR_TOKEN> nixpkgs-review pr <pr-number>`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Also not sure it makes sense to mention pr <pr-number> in the checklist since when a person is contributing, there is no PR-yet.

For “built on platforms”, I can do that before submitting the PR, but here it forces me to leave the terminal to go edit the pull request after submitting it. I use gh so my current workflow is running nix-build and then checking the checkboxes in the text editor, before submitting.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This looks like a good workflow. However:

  • The pullrequesters (now) iare encuraged to complete the same worfklow as the reviewers
  • That is, they are encouraged to nixpkgs-review post-result this is only available once the pr exists

This can't be addressed in this PR, but it might make sense to support creating a PR with nixpkgs-review altogether so that already the commit message can combine:

  • PR template for the respective PR type (module update, package update, new, etc) with type-specific check boxes
  • concatenated with the result of the nixpkgs-review evaluation

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

Well, there is nixpkgs-review rev HEAD which can be used by the pullrequester, maybe we could add a comment like <!-- you can use `nixpkgs-review rev HEAD` to run the tests before PR is opened -->

.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
- [ ] Ensured that relevant documentation is up to date
- [ ] other Linux (Ubuntu, Archlinux, Alpine, etc.).

- [ ] If available: tested via one or more NixOS test(s) `GITHUB_TOKEN=<YOUR_TOKEN> nixpkgs-review pr -p nixosTests.<test> <package> <pr-number>` (look inside [nixos/tests](https://github.com/NixOS/nixpkgs/blob/master/nixos/tests)
Copy link
Contributor

Choose a reason for hiding this comment

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

We might also want to mention passthru.tests. Or implement Mic92/nixpkgs-review#77 and add the mapping to every package with NixOS test.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Could you make a suggestion until the mentioned PR is merged, or should we just be pationt until then and leave this as it is?

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we could add a comment like “look for passthru.tests within the package expression” or “try running nix-build -A <package>.tests”. Or just ignore it for now, since ofborg will already run passthru.tests so there is not much need to run them locally. I guess that is fine, no need to ask reviewers to do what machines can.

.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
David Arnold and others added 8 commits July 7, 2020 18:46
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
This is since for some reviewers, memory usage is fencing off it's usage
@blaggacao
Copy link
Contributor Author

I have a better idea, am preparing PR with all the feedback incorporated.

@blaggacao blaggacao closed this Jul 8, 2020
- [ ] other Linux distributions (Ubuntu, Arch Linux, Alpine, etc.).

- [ ] If available: tested via one or more NixOS test(s) `nixpkgs-review pr -p nixosTests.<test> <package> <pr-number>` (look inside [nixos/tests](https://github.com/NixOS/nixpkgs/blob/master/nixos/tests)
<!-- Note, that only few tests are available, if you'd want to write your own have a look at: https://github.com/NixOS/nixpkgs/issues/34987 and furthermore read through https://nixos.org/nixos/manual/index.html#sec-nixos-tests. Looking through the source code should be helpful as well. -->
Copy link
Contributor

Choose a reason for hiding this comment

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

Really, the installed tests are only relevant to fraction of GNOME and GNOME-adjacent software, most of which already has a package so I would not waste characters on promoting it here. Saying that as person interested in these tests.

@blaggacao
Copy link
Contributor Author

Superseded by #92676

@blaggacao blaggacao deleted the patch-2 branch August 1, 2021 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants