fix line and import

.github/CONTRIBUTING.md

@@ -1,29 +1,28 @@
-
 # How to contribute
 
 ## Getting Started
 
 * Make sure you have a [GitHub account](https://github.com/signup/free)
 * Submit a ticket for your issue, assuming one does not already exist.
-  * Clearly describe the issue including steps to reproduce when it is a bug.
-  * Make sure you fill in the earliest version that you know has the issue.
+    * Clearly describe the issue including steps to reproduce when it is a bug.
+    * Make sure you fill in the earliest version that you know has the issue.
 * Fork the repository on GitHub
 
 ## Making Changes
 
 * Create a topic branch from where you want to base your work.
-  * This is usually the master branch.
-  * Only target release branches if you are certain your fix must be on that
-    branch.
-  * To quickly create a topic branch based on master; `git checkout -b
-    fix/master/my_contribution master`. Please avoid working directly on the
-    `master` branch.
+    * This is usually the master branch.
+    * Only target release branches if you are certain your fix must be on that
+      branch.
+    * To quickly create a topic branch based on master; `git checkout -b
+      fix/master/my_contribution master`. Please avoid working directly on the
+      `master` branch.
 * Make commits of logical units.
 * Check for unnecessary whitespace with `git diff --check` before committing.
 * Make sure your commit messages are in the proper format:
 
 `ISSUE-1234: terse and to the point message describing change`
-    
+
 * Make sure you have added the necessary tests for your changes.
 * Run _all_ the tests to assure nothing else was accidentally broken.
 * Make sure you've done a squash and rebase before submitting

.github/ISSUE_TEMPLATE.md

@@ -4,20 +4,25 @@
 <!--- Provide a brief summary of the issue in the title above -->
 
 ### Expected Behavior
+
 <!--- If you're describing a bug, tell us what should happen -->
 <!--- If you're suggesting a change/improvement, tell us how it should work -->
 
 ### Current Behavior
+
 <!--- If describing a bug, tell us what happens instead of the expected behavior -->
 <!--- If suggesting a change/improvement, explain the difference from current behavior -->
 
 ### Context
+
 <!--- How has this issue affected you? What are you trying to accomplish? -->
 <!--- Providing context helps us come up with a solution that is most useful in the real world -->
 
 ### Steps to Reproduce (for bugs)
+
 <!--- Provide a self-contained example project (as an attached archive or a Github project). -->
 <!--- In the rare cases where this is infeasible, we will also accept a detailed set of instructions. -->
 
 ### Your Environment
+
 <!--- Include as many relevant details about the environment you experienced the bug in -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,23 +2,26 @@ Please do not create a Pull Request without first creating an ISSUE.
 Any change needs to be discussed before proceeding.
 Failure to do so may result in the rejection of the Pull Request.
 
-Explain the **details** for making this change: What existing problem does the Pull Request solve? Why is this feature beneficial?
+Explain the **details** for making this change: What existing problem does the Pull Request solve? Why is this feature
+beneficial?
 
 **On adding new feautes/endpoints**
 
-No more than 1 endpoint should be coded within a Pull Request. 
-This alone requires enough code to review and adding more than 1 WILL result in your Pull Request either being ignored or rejected outright.
+No more than 1 endpoint should be coded within a Pull Request.
+This alone requires enough code to review and adding more than 1 WILL result in your Pull Request either being ignored
+or rejected outright.
 
 **On adding Mock and Integ Tests**
 
-At _least_ 2 mock tests and 2 integ tests are required prior to merging. 
+At _least_ 2 mock tests and 2 integ tests are required prior to merging.
 Each pair should should test what the success and failure of added change looks like.
 More complicated additions will of course require more tests.
 
 **On CI testing (currently using travis)**
 
 Code will not be reviewed until CI passes.
-Current CI does NOT exercise `integ` tests and so each Pull Request will have to be run manually by one of the maintainers to confirm it works as expected: please be patient.
+Current CI does NOT exercise `integ` tests and so each Pull Request will have to be run manually by one of the
+maintainers to confirm it works as expected: please be patient.
 
 **On automtatic closing of ISSUES**
 

.github/dependabot.yml

@@ -1,15 +1,15 @@
 version: 2
 updates:
-- package-ecosystem: gradle
-  directory: "/"
-  schedule:
-    interval: daily
-    time: "10:00"
-  open-pull-requests-limit: 10
-  ignore:
-  - dependency-name: com.google.inject.extensions:guice-assistedinject
-    versions:
-    - 5.0.0
-  - dependency-name: com.google.inject:guice
-    versions:
-    - 5.0.0
+  - package-ecosystem: gradle
+    directory: "/"
+    schedule:
+      interval: daily
+      time: "10:00"
+    open-pull-requests-limit: 10
+    ignore:
+      - dependency-name: com.google.inject.extensions:guice-assistedinject
+        versions:
+          - 5.0.0
+      - dependency-name: com.google.inject:guice
+        versions:
+          - 5.0.0

.github/workflows/github-actions.yaml

@@ -1,6 +1,6 @@
 name: Jenkins REST CI Build
 run-name: ${{ github.actor }} is running Jenkins REST CI Build on GitHub Actions 🚀
-on: [push, pull_request_target]
+on: [ push, pull_request_target ]
 permissions:
   checks: write
 jobs:

CODE_OF_CONDUCT.md

@@ -2,7 +2,10 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
+participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
+disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
 
 ## Our Standards
 
@@ -24,23 +27,35 @@ Examples of unacceptable behavior by participants include:
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take
+appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the
+project or its community. Examples of representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed representative at an online or offline
+event. Representation of a project may be further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hillel95med@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
+hillel95med@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it
+deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the
+reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent
+repercussions as determined by other members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available
+at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
+
 [version]: http://contributor-covenant.org/version/1/4/