Skip to content

CI: bump pre commit not black - #15998

Merged
nstarman merged 5 commits into
astropy:mainfrom
nstarman:ci-bump-pre-commit-not-black
Feb 14, 2024
Merged

nstarman merged 5 commits into
astropy:mainfrom
nstarman:ci-bump-pre-commit-not-black

Conversation

@nstarman

@nstarman nstarman commented Feb 6, 2024 •

Copy link
Copy Markdown
Member

Description

Partially addresses #15995.

  • 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.

Signed-off-by: nstarman <[email protected]>
@github-actions

github-actions Bot commented Feb 6, 2024

Copy link
Copy Markdown
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?
  • Is a milestone set? Milestone must be set but we cannot check for it on Actions; do not let the green checkmark fool you.
  • 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.

@github-actions

github-actions Bot commented Feb 6, 2024

Copy link
Copy Markdown
Contributor

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

Signed-off-by: nstarman <[email protected]>
Signed-off-by: nstarman <[email protected]>
@nstarman
nstarman force-pushed the ci-bump-pre-commit-not-black branch from d8e8cfa to 67a106e Compare February 6, 2024 04:42
@nstarman
nstarman marked this pull request as ready for review February 6, 2024 04:59

@neutrinoceros neutrinoceros left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thank you for doing this !

Comment thread .ruff.toml Resolved
Comment thread .ruff.toml
"PERF401", # Use a list comprehension to create a transformed list

# pygrep-hooks (PGH)
"PGH001", # eval

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There is an ignore for this rule in pyproject.toml too:

"PGH001", # No builtin eval() allowed

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

✅

@mhvk mhvk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Mostly looks good, certainly fine for units and utils.

Comment thread astropy/io/ascii/daophot.py Resolved

@dhomeier dhomeier left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I am with @mhvk on better getting by without chain in io.ascii. Applying RUF018 in the cases here and for consistency is fine with me.

Comment thread astropy/io/ascii/daophot.py Resolved
Signed-off-by: nstarman <[email protected]>
@nstarman
nstarman force-pushed the ci-bump-pre-commit-not-black branch from b76a115 to 344c3cb Compare February 7, 2024 20:11

@mhvk mhvk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks, happy (enough) with this!

@eerovaher eerovaher left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'd prefer the commits to be squashed, but all my suggestions about the final state of the patch have been addressed.

@nstarman

nstarman commented Feb 7, 2024

Copy link
Copy Markdown
Member Author

Squash-commit!

@pllim

pllim commented Feb 7, 2024

Copy link
Copy Markdown
Member

@dhomeier requested changes, so maybe he should have another look?

@dhomeier dhomeier left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

My requests were about the suggestions from @mhvk already included, just one question remaining for consistency in daophot remaining.
But this is acceptable either way, thanks!

Comment thread astropy/io/ascii/daophot.py Resolved
@nstarman

Copy link
Copy Markdown
Member Author

Thanks all!

@nstarman
nstarman merged commit 9a03dab into astropy:main Feb 14, 2024
@nstarman
nstarman deleted the ci-bump-pre-commit-not-black branch February 14, 2024 01:43
d-giles referenced this pull request in d-giles/astropy-abdufork Jul 26, 2024
* bump pre-commit
* Apply updated pre-commit
* manual fixes
* manual fix RUF017

Signed-off-by: nstarman <[email protected]>
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.

6 participants