anchor.diff:  
   The Spring team takes a very conservative approach to accepting contributions to the framework. This is to keep code quality and stability as high as possible, and to keep complexity at a minimum. Your changes, if accepted, may be heavily modified prior to merging. You will retain "Author:" attribution for your Git commits granted that the bulk of your changes remain intact. You may be asked to rework the submission for style (as explained above) and/or substance. Again, we strongly recommend discussing any serious submissions with the Spring Framework team prior to engaging in serious development work.
   
  -Note that you can always force push (git push -f) reworked / rebased commits against the branch used to submit your pull request. i.e. you do not need to issue a new pull request when asked to make changes.
  +Note that you can always force push (`git push -f`) reworked / rebased commits against the branch used to submit your pull request. i.e. you do not need to issue a new pull request when asked to make changes.
  
positive.code: 
  = Squash commits
  
  Use git rebase –interactive, git add –patch and other tools to "squash" multiple commits into atomic changes. In addition to the man pages for git, there are many resources online to help you understand how these tools work. Here is one: https://book.git-scm.com/4_interactive_rebasing.html[https://book.git-scm.com/4_interactive_rebasing.html].
  
  = Use real name in git commits
  
  Please configure git to use your real first and last name for any commits you intend to submit as pull requests. For example, this is not acceptable:
  
  Rather, please include your first and last name, properly capitalized, as submitted against the SpringSource contributor license agreement:
  <pre>
  Author: First Last &lt;link:mailto:&#x75;&#115;&#101;&#114;&#64;&#109;&#x61;&#x69;&#108;&#46;&#99;&#111;&#x6d;&#38;&#103;&#116;[&#x75;&#115;&#101;&#114;&#64;&#109;&#x61;&#x69;&#108;&#46;&#99;&#111;&#x6d;&#38;&#103;&#116;];
  </pre>
  This helps ensure traceability against the CLA, and also goes a long way to ensuring useful output from tools like git shortlog and others.
  
  You can configure this globally via the account admin area GitHub (useful for fork-and-edit cases); globally with
  
  or locally for the spring-security repository only by omitting the '–global' flag:
  <pre>
  cd spring-security
  git config user.name "First Last"
  git config user.email link:mailto:&#x75;&#115;&#101;&#x72;&#64;&#x6d;&#x61;&#x69;&#x6c;&#46;&#x63;&#111;&#109;[&#x75;&#115;&#101;&#x72;&#64;&#x6d;&#x61;&#x69;&#x6c;&#46;&#x63;&#111;&#109;]
  </pre>
  
  = Format commit messages
  
  . Keep the subject line to 50 characters or less if possible
  . Do not end the subject line with a period
  . In the body of the commit message, explain how things worked before this commit, what has changed, and how things work now
  . Include Closes gh-<issue-number> at the end if this fixes a GitHub issue
  . Avoid markdown, including back-ticks identifying code
  
  = Run all tests prior to submission
  
  = Submit your pull request
  
  Subject line:
  
  Follow the same conventions for pull request subject lines as mentioned above for commit message subject lines.
  
  In the body:
  
  . Explain your use case. What led you to submit this change? Why were existing mechanisms in the framework insufficient? Make a case that this is a general-purpose problem and that yours is a general-purpose solution, etc
  . Add any additional information and ask questions; start a conversation, or continue one from GitHub Issues
  
negative.code: 
  = Code of Conduct
  
  Please see our https://github.com/spring-projects/.github/blob/master/CODE_OF_CONDUCT.md[code of conduct].
  
  = Similar but different
  
  Each Spring module is slightly different from one another in terms of team size, number of issues, etc. Therefore, each project is managed slightly different. You will notice that this document is very similar to the https://github.com/spring-projects/spring-framework/wiki/Contributor-guidelines[Spring Framework Contributor guidelines]. However, there are some subtle differences between the two documents, so please be sure to read this document thoroughly.
  
  = Importing into IDE
  
  The following provides information on setting up a development environment that can run the sample in https://www.springsource.org/sts[Spring Tool Suite 3.6.0+]. Other IDE's should work using Gradle's IDE support, but have not been tested.
  
  * IDE Setup
  ** Install Spring Tool Suite 3.6.0+
  ** You will need the following plugins installed (can be found on the Extensions Page)
  *** Gradle Eclipse
  *** Groovy Eclipse
  * Importing the project into Spring Tool Suite
  ** File -> Import… -> Gradle Project
  
  As of new versions of Spring Tool Suite, you might need to install Groovy Eclipse pointing directly to the updated plugin location. To install Groovy Eclipse on Spring Tool Suite based on Eclipse Oxigen you must do the following steps:
  
  Help -> Install New Software… -> Add the following URL into _Work with_ field:
  https://dist.springsource.org/snapshot/GRECLIPSE/e4.7/[https://dist.springsource.org/snapshot/GRECLIPSE/e4.7/]
  
  = Understand the basics
  