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

update pull request checklist #1336

Conversation

zacharyburnett
Copy link
Collaborator

@zacharyburnett zacharyburnett commented Jul 30, 2024

analogous to spacetelescope/jwst#8670

old checklist


Checklist

  • added entry in CHANGES.rst under the corresponding subsection
  • [N/A] updated relevant tests
  • updated relevant documentation
  • updated relevant milestone(s)
  • added relevant label(s)
  • [N/A] ran regression tests, post a link to the Jenkins job below. How to run regression tests on a PR

new checklist


Tasks

  • request a review from someone specific, to avoid making the maintainers review every PR
  • add a build milestone, i.e. 24Q4_B15 (use the latest build if not sure)
  • Does this PR change user-facing code / API? (if not, label with no-changelog-entry-needed)
    • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see below for change types)
    • update or add relevant tests
    • update relevant docstrings and / or docs/ page
    • start a regression test and include a link to the running job (click here for instructions)
      • Do truth files need to be updated ("okified")?
        • after the reviewer has approved these changes, run okify_regtests to update the truth files
  • if a JIRA ticket exists, make sure it is resolved properly
news fragment change types...
  • changes/<PR#>.general.rst: infrastructure or miscellaneous change
  • changes/<PR#>.docs.rst
  • changes/<PR#>.stpipe.rst
  • changes/<PR#>.associations.rst
  • changes/<PR#>.scripts.rst
  • changes/<PR#>.mosaic_pipeline.rst
  • changes/<PR#>.patch_match.rst

steps

  • changes/<PR#>.dq_init.rst
  • changes/<PR#>.saturation.rst
  • changes/<PR#>.refpix.rst
  • changes/<PR#>.linearity.rst
  • changes/<PR#>.dark_current.rst
  • changes/<PR#>.jump_detection.rst
  • changes/<PR#>.ramp_fitting.rst
  • changes/<PR#>.assign_wcs.rst
  • changes/<PR#>.flatfield.rst
  • changes/<PR#>.photom.rst
  • changes/<PR#>.flux.rst
  • changes/<PR#>.source_detection.rst
  • changes/<PR#>.tweakreg.rst
  • changes/<PR#>.skymatch.rst
  • changes/<PR#>.outlier_detection.rst
  • changes/<PR#>.resample.rst
  • changes/<PR#>.source_catalog.rst

@zacharyburnett zacharyburnett self-assigned this Jul 30, 2024
@zacharyburnett zacharyburnett added this to the 24Q4_B15 milestone Jul 30, 2024
@zacharyburnett zacharyburnett marked this pull request as ready for review July 30, 2024 13:32
@zacharyburnett zacharyburnett requested a review from a team as a code owner July 30, 2024 13:32
Copy link

codecov bot commented Jul 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.46%. Comparing base (908f0f9) to head (6ae2a84).
Report is 33 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1336   +/-   ##
=======================================
  Coverage   78.46%   78.46%           
=======================================
  Files         117      117           
  Lines        7866     7866           
=======================================
  Hits         6172     6172           
  Misses       1694     1694           
Flag Coverage Δ *Carryforward flag
nightly 62.24% <ø> (ø) Carriedforward from 908f0f9

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@ddavis-stsci ddavis-stsci left a comment

Choose a reason for hiding this comment

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

I think adding the build milestone is good.
Otherwise my impression is that most of this is too "in the weeds" for a checklist.
I'd add most of this to the "Tickets & PR" section of https://innerspace.stsci.edu/pages/viewpage.action?spaceKey=SCSB&title=Roman+Calibration+Pipeline
That page is more easily updated and flexible. Having the checklist be more generic also solves the problem of trying to keep both in sync.

@zacharyburnett
Copy link
Collaborator Author

I think adding the build milestone is good. Otherwise my impression is that most of this is too "in the weeds" for a checklist. I'd add most of this to the "Tickets & PR" section of https://innerspace.stsci.edu/pages/viewpage.action?spaceKey=SCSB&title=Roman+Calibration+Pipeline That page is more easily updated and flexible. Having the checklist be more generic also solves the problem of trying to keep both in sync.

That is good to have it on Innerspace; however, I think it is more important to have the checklist here as well, both to have the checklist be immediately visible (and less easily forgettable) and also have it accessible to outside contributors who can't see the Innerspace page. If I had a choice between keeping the checklist here or on Innerspace, I personally would choose here for that reason; however, I will yield to your suggestion if you think that is better

@ddavis-stsci
Copy link
Collaborator

ddavis-stsci commented Aug 2, 2024 via email

@zacharyburnett zacharyburnett force-pushed the update/pull_request_template branch 4 times, most recently from d40849a to 6bbab79 Compare September 9, 2024 13:27
move checklist instructions to comment

update link to romancal
Copy link
Collaborator

@schlafly schlafly left a comment

Choose a reason for hiding this comment

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

Approving since this has also gone in on the Webb side.

@zacharyburnett zacharyburnett merged commit 3107d3d into spacetelescope:main Sep 24, 2024
30 checks passed
@zacharyburnett
Copy link
Collaborator Author

@zacharyburnett zacharyburnett deleted the update/pull_request_template branch September 24, 2024 16:09
mairanteodoro pushed a commit to mairanteodoro/romancal that referenced this pull request Oct 7, 2024
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.

3 participants