Update section 2.3 to clarify allowed character set #470
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
larsbarring
force-pushed
the
update_sect_2.3
branch
from
200b8c4 to
f1d5e3e
Compare
larsbarring
force-pushed
the
update_sect_2.3
branch
3 times, most recently
from
5ca0e65 to
d76c268
Compare
ethanrd
requested changes
Nov 9, 2023
larsbarring
force-pushed
the
update_sect_2.3
branch
2 times, most recently
from
4f84283 to
72de2b7
Compare
larsbarring
force-pushed
the
update_sect_2.3
branch
from
72de2b7 to
858864f
Compare
|
@ethanrd may I ask you to once again have a look at the updated PR, and if nothing comes up then merge this. Many thanks. Cheers / Lars |
|
Looks good. Thanks @larsbarring! |
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.
See issue #468 for discussion of these changes.
Release checklist
cf-conventions.adoc?cf-conventions.adocup to date? Versioning inspired by SemVer.history.adocup to date?For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then,
mainalways is a draft for the next version.