Updated contributions.md and .gitignore (#34)

* Update contributions.md

* Update .gitignore and steps in contributions.md

Author: borjaocejo

.gitignore

@@ -2,3 +2,5 @@
 build/
 docs/_build/
 .gradle/
+.idea/
+.vscode/

contributions.md

@@ -22,23 +22,22 @@ and sent to [[email protected]](mailto:[email protected]?subject=Vulnera
 preferably with the title "Vulnerability in Github LinkedIn/DuaLip - < short summary >".
 
 ## Steps for Creating Pull Request
-1. Test build. (./gradlew build)
-2. Create a new branch locally. (git branch mybranch)
-3. Commit the changes locally. (git commit)
-4. **Don't forget to update project.version in build.gradle.** We follow the semantic versioning (major.minor.patch). 
+1. Create a new local branch (git branch mybranch)
+2. Make code changes in local branch
+3. **Change major and/or minor version in `version.properties` if necessary**.
+   We follow semantic versioning practices (major.minor.patch).
    * Increment Major for backward incompatible change.
    * Increment Minor for major function changes.
-   * Increment Patch for bug fixes.
-5. **Also, don't forget to create a corresponding new tag locally and push to the original master.**
-   * git tag vx.x.x
-   * git push origin vx.x.x
+   * Patch versionining and releases are handled automatically by CI/CD flows.
+4. Commit changes to local branch (git commit)
+5. Test build (./gradlew build)
 6. Push local changes to remote branch. (git push -f origin mybranch)
 7. Create a new pull request at https://github.com/linkedin/DuaLip/pulls
-8. If need to update the pull request, repeat step 2 to 3.
+8. If you need to update the pull request, repeat steps 2 through 6, **excluding step 3**.
 9. Getting review and approval. Squash and merge to main branch.
 
 ## Tips for Getting Your Pull Request Accepted
 
 1. Make sure all new features are tested and the tests pass.
 2. Bug fixes must include a test case demonstrating the error that it fixes.
-3. Open an issue first and seek advice for your change before submitting a pull request. Large features which have never been discussed are unlikely to be accepted. 
+3. Open an issue first and seek advice for your change before submitting a pull request. Large features which have never been discussed are unlikely to be accepted.