Make substitution fields more prominent and distinct from true 'skeleton' references #71
Conversation
This file contains 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
jaraco
commented
Nov 24, 2022
jaraco
force-pushed
the
feature/prominent-fields
branch
from
6a6e23a
to
6da8d02
Compare
|
In the latest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In this change, I'm pondering making the fields more prominent.
I have to say, I'm not excited about the prospect of all of the merge conflicts this will create, so I'll almost certainly not merge it until I have confidence I can automate the resolution of merge conflicts. In https://github.com/jaraco/jaraco.develop/blob/66be40935bbe0904999d035c05f4bdccd1a7d89d/jaraco/develop/merge.py#L69-L73, I've had some success with mechanized resolution.