<commit_before>= Spring Data contribution guidelines

[[code-of-conduct]]
== Code of Conduct

This project adheres to the Contributor Covenant link:CODE_OF_CONDUCT.adoc[code of conduct].
By participating, you  are expected to uphold this code.
Please report unacceptable behavior to <EMAIL>.

[[quickstart]]
== Quickstart

For the impatient, if you want to submit a quick pull request:

* Make sure there is a ticket in the bug tracker for the project in our https://jira.spring.io[JIRA].
* Make sure you use the code formatters provided https://github.com/spring-projects/spring-data-build/tree/master/etc/ide[here] and have them applied to your changes. Don't submit any formatting related changes.
* Make sure you submit test cases (unit or integration tests) that back your changes.
* Try to reuse existing test sample code (domain classes). Try not to amend existing test cases but create new ones dedicated to the changes you're making to the codebase. Try to test as locally as possible but potentially also add integration tests.
* In the Javadoc for the newly added test cases refer to the ticket the changes apply to like this

[source, java]
----
@Test // DATA…-???
public void yourTestMethod() { … }
----

* Make sure you added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).
* The commit message should follow the following style:
** First line starts with the ticket id.
** Separate ticket id and summary with a dash.
** Finish summary with a dot.
** In the description, don't use single line breaks. No manual wrapping. Separate paragraphs by a blank line.
** Add related references at the very bottom (also see the section on pull requests below).

[source]
----
DATA…-??? - Summary of the commit (try to stay under 80 characters).

Additional explanations if necessary.

See also: DATA…-???. (optionally refer to related tickets)
----

* Make sure you provide your full name and an email address registered with your GitHub account.
If you're a first-time submitter, make sure you have signed the https://cla.pivotal.io/sign/spring[Contributor License Agreement].

[[advanced]]
== Advanced

This section contains some advanced information, mainly targeted at developers of the individual projects.
<commit_msg>#584 - Improved contribution guidelines on commit messages.<commit_after>= Spring Data contribution guidelines

[[code-of-conduct]]
== Code of Conduct

This project adheres to the Contributor Covenant link:CODE_OF_CONDUCT.adoc[code of conduct].
By participating, you  are expected to uphold this code.
Please report unacceptable behavior to <EMAIL>.

[[quickstart]]
== Quickstart

For the impatient, if you want to submit a quick pull request:

* Make sure there is a ticket in the bug tracker for the project in our https://jira.spring.io[JIRA].
* Make sure you use the code formatters provided https://github.com/spring-projects/spring-data-build/tree/master/etc/ide[here] and have them applied to your changes. Don't submit any formatting related changes.
* Make sure you submit test cases (unit or integration tests) that back your changes.
* Try to reuse existing test sample code (domain classes). Try not to amend existing test cases but create new ones dedicated to the changes you're making to the codebase. Try to test as locally as possible but potentially also add integration tests.
* In the Javadoc for the newly added test cases refer to the ticket the changes apply to like this

[source, java]
----
@Test // DATA…-???
public void yourTestMethod() { … }
----

* Make sure you added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).
* Make sure you follow the <<commit-messages>> guidelines.
* Make sure you provide your full name and an email address registered with your GitHub account.
If you're a first-time submitter, make sure you have signed the https://cla.pivotal.io/sign/spring[Contributor License Agreement].

[[commit-messages]]
== Commit messages

The commit message should follow the following style:
* First line starts with the ticket id.
* Separate ticket id and summary with a dash.
* Start summary with a capital letter.
* Finish summary with a dot.
* In the description, don't use single line breaks. No manual wrapping. Separate paragraphs by a blank line.
* During merges, add a reference to the original pull request.
* Add related references at the very bottom (also see the section on pull requests below).

[source]
----
DATA…-??? - Summary of the commit (try to stay under 80 characters).

Additional explanations if necessary.

Original pull reuqest: #??.
Related tickets: DATA…-???. (optionally refer to related tickets)
----

[[advanced]]
== Advanced

This section contains some advanced information, mainly targeted at developers of the individual projects.

{'fraction_non_alphanumeric': 0.0736135780540754, 'fraction_numerical': 0.001381488059996053, 'mean_word_length': 4.290187891440501, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6296747', 'n_tokens_mistral': 1294, 'n_tokens_neox': 1233, 'n_words': 719}