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

Remove items not relevant to documentation in PR template #234

Merged
merged 6 commits into from
Sep 18, 2023

Conversation

lucyleeow
Copy link
Collaborator

@lucyleeow lucyleeow commented Aug 21, 2023

Description

Remove items not relevant to documentation in PR template
Also makes check list just a list, like napari/napari#6092 did

Type of change

  • Fixes or improves existing content
  • Adds new content page(s)
  • Fixes or improves workflow, documentation build or deployment

References

Final checklist:

  • My PR is the minimum possible work for the desired functionality
  • I have commented my code, particularly in hard-to-understand areas
  • I have added alt text to new images included in this PR

@brisvag
Copy link
Contributor

brisvag commented Aug 21, 2023

@lucyleeow actually, would you mind updating this to match the changes in napari/napari#6092?

@brisvag
Copy link
Contributor

brisvag commented Aug 21, 2023

Which reminds me: @Czaki, should we update the label checking CI here as well?

@@ -1,8 +1,6 @@
# Description
<!-- What does this pull request (PR) do? Why is it necessary? -->
<!-- Tell us about your new content, improvement, or fix! -->
<!-- If you can, please add an image, or an animation "An image is worth a thousand words!" -->
<!-- You can use https://www.cockos.com/licecap/ or similar to create animations -->
Copy link
Member

Choose a reason for hiding this comment

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

I'm actually not sure about this. In documentation it is even more important to add images, so why not leave this in?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ah I read this as add images to the github PR thread - e.g., over in napari, people may put a screenshot/video capture in a comment to demonstrate what their code does. I thought here, if an image is added we could just look at it in the file tab. Though now that I think about it maybe with lfs we won't be able to see the image? (I am really not familiar with lfs).

Maybe it is worth a slight re-wording to clarify what we mean (esp as I think we mean something different when we say this over in napari?)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Related, do we have documentation on how to deal with lfs when contributing images in docs?

Copy link
Member

Choose a reason for hiding this comment

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

We are not using lfs anymore, so this shouldn't be a problem. I read this comment as "Please add images to the documentation page you are writing if you can", but maybe I am missing the perspective of the user here - they may understand like you did. So not sure!

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've updated it slightly and kept this, thanks for your review!

Comment on lines -19 to -21
- [ ] My PR is the minimum possible work for the desired functionality
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added [alt text](https://webaim.org/techniques/alttext/) to new images included in this PR
Copy link
Member

Choose a reason for hiding this comment

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

No strong feelings here, but we did include this thinking of tooling/infrastructure PRs (dealing with sphinx, sphinx-gallery, CI etc).

Copy link
Collaborator Author

@lucyleeow lucyleeow Aug 22, 2023

Choose a reason for hiding this comment

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

Don't feel strongly here either but would like to remove the checklist as I think doc only PRs would be most common and I never know what I am mean to do (with the irrelevant checklist items) in that case.

Maybe a minor re-word also here to make these more relevant E.g., comment code so others know what it achieves

Could we also add a 'if the PR relates to tooling/infrastructure changes:' before the items - because when I make a doc PR the first 2 items seem a bit awkward/confusing to me?

@Czaki
Copy link
Contributor

Czaki commented Aug 22, 2023

Which reminds me: @Czaki, should we update the label checking CI here as well?

I suggest yes.

@lucyleeow
Copy link
Collaborator Author

actually, would you mind updating this to match the changes in napari/napari#6092?

@brisvag done!

Copy link
Contributor

@brisvag brisvag left a comment

Choose a reason for hiding this comment

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

Great!

Copy link
Member

@melissawm melissawm left a comment

Choose a reason for hiding this comment

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

Thanks @lucyleeow !

@psobolewskiPhD psobolewskiPhD added this to the 0.4.19 milestone Sep 14, 2023
@psobolewskiPhD psobolewskiPhD merged commit 4602d9b into napari:main Sep 18, 2023
6 checks passed
@lucyleeow lucyleeow deleted the tmplate branch September 18, 2023 01:01
@psobolewskiPhD psobolewskiPhD modified the milestones: 0.4.19, 0.5.0 Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants