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

Move new warning after example of previous warning [ci-skip] #49884

Merged
merged 1 commit into from Nov 1, 2023

Conversation

p8
Copy link
Member

@p8 p8 commented Nov 1, 2023

We probably also want to add headings for these warnings, to clarify where sections begin/end.

Checklist

Before submitting the PR make sure the following are checked:

  • This Pull Request is related to one change. Changes that are unrelated should be opened in separate PRs.
  • Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: [Fix #issue-number]
  • Tests are added or updated if you fix a bug or add a feature.
  • CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.

@rails-bot rails-bot bot added the docs label Nov 1, 2023
@p8 p8 changed the title Move new warning after example of previous wanring [ci-skip] Move new warning after example of previous warning [ci-skip] Nov 1, 2023
@p8 p8 merged commit 44f914b into rails:main Nov 1, 2023
3 checks passed
@p8 p8 deleted the guides/move-after-commit-warning branch November 1, 2023 13:23
@adrianna-chang-shopify
Copy link
Contributor

Thanks Petrik ❤️

@@ -585,6 +573,18 @@ irb> @user.save # updating @user
User was saved to database
```

WARNING. In the context of a single transaction, if you interact with multiple
Copy link
Member

Choose a reason for hiding this comment

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

This is maybe for another PR, but I find these huge walls of text (especially in a note/warning block) with no sample code to be difficult to catch.

Copy link
Member Author

Choose a reason for hiding this comment

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

I agree.

p8 added a commit to p8/rails that referenced this pull request Nov 4, 2023
Move new warning after example of previous wanring [ci-skip]
p8 added a commit that referenced this pull request Nov 4, 2023
…49912)

Move new warning after example of previous wanring [ci-skip]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants