8000 Fix typos in quantity tests by larrybradley · Pull Request #17394 · astropy/astropy · GitHub
[go: up one dir, main page]

Skip to content

Fix typos in quantity tests#17394

Merged
pllim merged 1 commit intoastropy:mainfrom
larrybradley:fix-typos
Nov 14, 2024
Merged

Fix typos in quantity tests#17394
pllim merged 1 commit intoastropy:mainfrom
larrybradley:fix-typos

Conversation

@larrybradley
Copy link
Member

Description

I'm late to the party, but this PR fixes a couple of typos introduced in #17354. I'm not sure if it's necessary to backport this.

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

@github-actions
Copy link
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

Copy link
Member
@pllim pllim left a comment

Choose a reason for hiding this comment

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

Does not hurt to backport. Thanks!

@pllim pllim enabled auto-merge November 14, 2024 15:02
Copy link
Contributor
@neutrinoceros neutrinoceros left a comment

Choose a reason for hiding this comment

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

Thanks ! I propose to backport anyway, if only to reduce the chance of a conflict down the line.

@pllim
Copy link
Member
pllim commented Nov 14, 2024

For the sake of consistency, let's do v6.1.x as well.

@meeseeksdev backport to v6.1.x

meeseeksmachine pushed a commit to meeseeksmachine/astropy that referenced this pull request Nov 14, 2024
@pllim pllim modified the milestones: v7.0.0, v6.1.7 Nov 14, 2024
pllim added a commit that referenced this pull request Nov 14, 2024
…394-on-v7.0.x

Backport PR #17394 on branch v7.0.x (Fix typos in quantity tests)
pllim added a commit that referenced this pull request Nov 14, 2024
…394-on-v6.1.x

Backport PR #17394 on branch v6.1.x (Fix typos in quantity tests)
@larrybradley larrybradley deleted the fix-typos branch November 14, 2024 15:44
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

0