Missing Installation and ContributingGuidelines?

I forked and cloned this repo locally, then tried to find the installation procedure. Unfortunately, I did Java coding long ago and thus installing this locally isn’t trivial to me right now, or I didn’t look properly. I think it would be worth while to have a separate file like INSTALL for folks who haven’t written production-level Java code so that they can compile locally. Also, I was checking out PRs and it looks as if there are some conventions like first merging into develop and then when it looks stable, merging that branch with master which is also not trivial. I think a ContributingGuidelines can go a long way.

Any thoughts?

[athityakumar]

Acknowledged. I’ll try to send in a PR by this weekend.

Regarding the guideline of submitting all PRs against the develop branch, I think it’d be a good idea to additionally specify this in a .github/PULL_REQUEST_TEMPLATE.md file too. When a new PR is about to be submitted, this template file content is shown as the new PR’s placeholder (default) description and could be more effective in communicating this message across to the contributors.

[ptrthomas]

@pranitbauva1997 @athityakumar great !

do consider submitting a PR for a small doc - and looks like the GitHub standard is a CONTRIBUTING.md file so I have just checked in a placeholder: https://github.com/intuit/karate/blob/develop/CONTRIBUTING.md

One guideline I’d like to mention is all PR-s should be submitted against the develop branch.

edit: added link to GitHub recommendations: https://help.github.com/articles/setting-guidelines-for-repository-contributors/