docs: no need to bump rebar.config when in couchdb.git

1 files changed, 4 insertions, 6 deletions

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index bda2e1121..71ea992ff 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,9 +1,9 @@
 <!-- Thank you for your contribution!
-     
+
      Please file this form by replacing markdown commentary
      tags with the text. If section needs in no action - remove it.
 
-     Also remember, that CouchDB uses the Review-Then-Commit (RTC) model 
+     Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
      of code collaboration. Positive feedback provides by +1 from committers
      while negative by -1. The -1 also means veto and need to be addressed
      to find the consensus. Once there are no objections, PR could be merged.
@@ -18,7 +18,7 @@
 ## Testing recommendations
 
 <!-- Describe how we can test your changes.
-     Does it provides any behaviour that the end users 
+     Does it provides any behaviour that the end users
      could notice? -->
 
 ## JIRA issue number
@@ -29,7 +29,7 @@
 
 ## Related Pull Requests
 
-<!-- If your changes affects on multiple components in different 
+<!-- If your changes affects on multiple components in different
      repositories please list here links to those pull requests.  -->
 
 ## Checklist
@@ -37,5 +37,3 @@
 - [ ] Code is written and works correctly;
 - [ ] Changes are covered by tests;
 - [ ] Documentation reflects the changes;
-- [ ] I will not forget to update [rebar.config.script](https://github.com/apache/couchdb/blob/master/rebar.config.script)
-      with the correct commit hash once this PR get merged.