= Spring Session MongoDB Examples
image:https://travis-ci.org/spring-projects/spring-session-data-mongodb-examples.svg?branch=main["Build Status", link="https://travis-ci.org/spring-projects/spring-session-data-mongodb-examples"]
This repository is a collection of examples using Spring Session MongoDB, allowing you to persist session data in a MongoDB instance.
== Examples
== Contributing
Spring Session MongoDB Examples is released under the non-restrictive Apache 2.0 license, and follows a very standard Github development process, using Github tracker for issues and merging pull requests into main. If you want to contribute even something trivial please do not hesitate, but follow the guidelines below.
=== Sign the Contributor License Agreement
Before we accept a non-trivial patch or pull request we will need you to sign the https://cla.pivotal.io/sign/spring[Contributor License Agreement]. Signing the contributor's agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.
=== Code of Conduct
This project adheres to the Contributor Covenant https://github.com/spring-projects/spring-session-data-mongodb/blob/main/CODE_OF_CONDUCT.adoc[code of conduct]. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
=== Code Conventions and Housekeeping
None of these is essential for a pull request, but they will all help. They can also be added after the original pull request but before a merge.
eclipse-code-formatter.xml
file from the https://raw.githubusercontent.com/spring-projects/spring-data-build/main/etc/ide/eclipse-formatting.xml[Spring Data Build] project. If using IntelliJ, you can use the https://plugins.jetbrains.com/plugin/6546[Eclipse Code Formatter Plugin] to import the same file..java
files to have a simple Javadoc class comment with at least an @author
tag identifying you, and preferably at least a paragraph on what the class is for..java
files (copy from existing files in the project)@author
to the .java files that you modify substantially (more than cosmetic changes).Fixes gh-XXXX
at the end of the commit message (where XXXX is the issue number).