You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Semantic line breaks make it easier to keep track of edits to prose text, when using git diff and similar tools.
If there were clear line breaks before and after each sentence or major phrase in the template, it would be easy to detect any added or removed phrases in a draft charter.
As an example, this paragraph:
<p>
Community Group participants agree to make all contributions in the
GitHub repo the group is using for the particular document. This may be
in the form of a pull request (preferred), by raising an issue, or by
adding a comment to an existing issue.
</p>
could look like this with semantic breaks
<p>
Community Group participants agree to make all contributions
in the GitHub repo the group is using for the particular document.
This may be
in the form of a pull request (preferred),
by raising an issue,
or
by adding a comment to an existing issue.
</p>
With this structure, edits to a single item in the list, or to the description of the repo location,
can often be isolated to a single line in the source code
The text was updated successfully, but these errors were encountered:
Semantic line breaks make it easier to keep track of edits to prose text, when using
git diff
and similar tools.If there were clear line breaks before and after each sentence or major phrase in the template, it would be easy to detect any added or removed phrases in a draft charter.
As an example, this paragraph:
could look like this with semantic breaks
With this structure, edits to a single item in the list, or to the description of the repo location,
can often be isolated to a single line in the source code
The text was updated successfully, but these errors were encountered: