Update patch naming documentation #231
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hturner
approved these changes
Jun 13, 2025
Member
hturner
left a comment
hturner
left a comment
There was a problem hiding this comment.
Thanks, I made a couple of minor edits to remove the quote formatting and put the file extension in code mark-up as we do for filename in general.
Collaborator
Author
|
Sure Heather, Thanks!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the "Creating a Patch File" tutorial to recommend using descriptive patch names that include the bug number and a short description (e.g., 16629-infinite-recursion.diff) instead of generic names like patch.diff.
This follows R Core best practices and helps reviewers quickly identify and track patches.
Closes #220.