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

Followup / fixup: apply 'black' code formatting to a couple of missed docstrings #1228

Closed
wants to merge 3 commits into from
Closed

Followup / fixup: apply 'black' code formatting to a couple of missed docstrings #1228

wants to merge 3 commits into from

Conversation

jayaddison
Copy link
Contributor

Description

Follow-up / completion of #1220. That change updated a number of docstrings within the codebase to use standardised black code formatting, but a couple of locations had been missed.

Checklist

This pull request is:

  • A documentation / typographical error fix
    • Good to go, no issue or tests are needed

…t' snippet in Operation.create_table docstring

Follows-on-from commit 84462ee.
…e_primary_key snippet, allowing it to fit on a single line

Follows-on-from commit 84462ee.
@CaselIT CaselIT requested review from sqlalchemy-bot and sqla-tester and removed request for sqlalchemy-bot April 26, 2023 20:29
Copy link
Collaborator

@sqla-tester sqla-tester left a comment

Choose a reason for hiding this comment

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

OK, this is sqla-tester setting up my work on behalf of CaselIT to try to get revision f5696b9 of this pull request into gerrit so we can run tests and reviews and stuff

@sqla-tester
Copy link
Collaborator

New Gerrit review created for change f5696b9: https://gerrit.sqlalchemy.org/c/sqlalchemy/alembic/+/4587

@sqla-tester
Copy link
Collaborator

Gerrit review https://gerrit.sqlalchemy.org/c/sqlalchemy/alembic/+/4587 has been merged. Congratulations! :)

@jayaddison jayaddison deleted the issue-1220-followup/apply-overlooked-black-code-formatting branch April 28, 2023 20:31
@jayaddison
Copy link
Contributor Author

Thanks again @CaselIT!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants