cybercyst/jj
1
0
Fork 0
mirror of https://github.com/martinvonz/jj.git synced 2025-05-28 10:31:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Deployed 5f84c73 to prerelease with MkDocs 1.6.0 and mike 2.1.1

Browse Source
This commit is contained in:
jj-docs[bot] 2024-09-12 14:53:08 +00:00
parent 7c34223b3a
commit f570689190
2 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
prerelease/contributing/index.html
View File

@ -1764,9 +1764,16 @@ commit and the new feature in a different commit. If the refactoring itself
consists of many parts, try to separate out those into separate commits. You can
use <code>jj split</code> to do it if you didn't realize ahead of time how it should be
split up. Include tests and documentation in the same commit as the code they
test and document. The commit message should describe the changes in the commit;
test and document. </p>
<p>The commit message should describe the changes in the commit;
the PR description can even be empty, but feel free to include a personal
message.</p>
message. We write commit messages in an affected component style and don't use
<a href="www.conventionalcommits.org/en/v1.0.0/">conventional commits</a>. This means if
you modified a command in the CLI, use its name as the topic, e.g
<code>next/prev: &lt;your-modification&gt;</code> or <code>conflicts: &lt;your-modification&gt;</code>. We don't
currently have a specific guidelines on what to write in the topic field, but
the reviewers will help you provide a topic if you have difficulties choosing
it.</p>
<p>When you address comments on a PR, don't make the changes in a commit on top (as
is typical on GitHub). Instead, please make the changes in the appropriate
commit. You can do that by creating a new commit on top of the initial commit

2
prerelease/search/search_index.json
View File

File diff suppressed because one or more lines are too long