Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@pllim
Copy link
Collaborator

@pllim pllim commented Mar 26, 2025

There is no JIRA ticket. As discussed on Slack with @tapastro and @melanieclarke , the first checkbox below is no longer needed.

Tasks

  • request a review from someone specific, to avoid making the maintainers review every PR
  • add a build milestone, i.e. Build 12.0 (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 changelog readme for instructions)
    • 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

to ask for someone specific.

[ci skip]
@pllim pllim added this to the Build 12.0 milestone Mar 26, 2025
@pllim pllim requested a review from a team as a code owner March 26, 2025 17:49
@github-actions github-actions bot added the automation Continuous Integration (CI) and testing automation tools label Mar 26, 2025
Copy link
Collaborator

@melanieclarke melanieclarke left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for tidying up!

Copy link
Collaborator

@emolter emolter left a comment

Choose a reason for hiding this comment

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

Is this still under discussion? I personally very much like the check box to exist. There are two reasons:

  • Even though I get pinged on everything, it's useful to know if someone wants my input, specifically. Then I know both that I cannot just wait for someone else to review it, and that they perceive me as a relative expert, which (might) change how I review the changes
  • It reminds me to ping people that don't get pinged on everything, say, e.g., Mihai for resample changes

It's ok if that opinion is overruled, I can just remember on my own to request certain reviewers.

@melanieclarke
Copy link
Collaborator

Sure, we can discuss.

I'm happy to keep it if we can rephrase in a way that makes it clear that if you know who to tag, you should do so, and if you don't know who to tag, you don't have to.

@emolter
Copy link
Collaborator

emolter commented Mar 26, 2025

How about "Mark PR as Ready for Review. If you have a specific reviewer in mind, tag them."

@melanieclarke
Copy link
Collaborator

How about "Mark PR as Ready for Review. If you have a specific reviewer in mind, tag them."

I like the second half, but some folks don't initially submit PRs as draft and might be confused about what "Mark PR as Ready for Review" means. Maybe that needs to be a separate bullet to clarify? Or just leave that part out?

@emolter
Copy link
Collaborator

emolter commented Mar 26, 2025

I'm fine leaving it out, I only really cared about the second part

@pllim
Copy link
Collaborator Author

pllim commented Mar 26, 2025

So instead of removing, rename to the following?

- [ ] If you have a specific reviewer in mind, tag them.

@melanieclarke
Copy link
Collaborator

So instead of removing, rename to the following?

- [ ] If you have a specific reviewer in mind, tag them.

Yes, that's the proposal. Is that clear enough to you?

@pllim
Copy link
Collaborator Author

pllim commented Mar 26, 2025

Sounds good. I added a commit to that effect. Should you accept this PR, please "squash and merge". Thanks for the reviews!

@melanieclarke
Copy link
Collaborator

I'll wait and see if @tapastro wants to comment, but the new proposal looks fine to me.

@melanieclarke
Copy link
Collaborator

I'll go ahead and get this merged now. We can always revise again later if needed.

@melanieclarke melanieclarke changed the title Remove outdated task from PR template to ask for someone specific Revise phrasing for specific reviews in PR task list Mar 28, 2025
@melanieclarke melanieclarke enabled auto-merge (squash) March 28, 2025 13:20
@melanieclarke melanieclarke merged commit b54dbba into spacetelescope:main Mar 28, 2025
25 checks passed
@codecov
Copy link

codecov bot commented Mar 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.69%. Comparing base (86af1f2) to head (0a18522).
Report is 742 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9328   +/-   ##
=======================================
  Coverage   74.69%   74.69%           
=======================================
  Files         369      368    -1     
  Lines       37117    37106   -11     
=======================================
- Hits        27723    27717    -6     
+ Misses       9394     9389    -5     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@pllim pllim deleted the no-one branch March 28, 2025 14:10
@pllim
Copy link
Collaborator Author

pllim commented Mar 28, 2025

Thanks for the feedback!

taylorbell57 pushed a commit to taylorbell57/jwst that referenced this pull request Apr 30, 2025
taylorbell57 pushed a commit to taylorbell57/jwst that referenced this pull request Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation Continuous Integration (CI) and testing automation tools no-changelog-entry-needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants