Skip to content

Commit

Permalink
KEYCLOAK-5789 Update PR policy (keycloak#4634)
Browse files Browse the repository at this point in the history
  • Loading branch information
@hmlnarik @stianst
hmlnarik authored and stianst committed Nov 7, 2017
1 parent b1a05df commit afb4a59
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions misc/HackingOnKeycloak.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,9 @@ Here's a quick check list for a good pull request (PR):
* All tests in testsuite pass
* Do a rebase on upstream master
* We only accept contributions to the master branch. The exception to this is if the fix is for the latest CR release and Final has not yet been released, in which case you can send the PR to both the corresponding branch and the master branch.
* PR needs to be accompanied with tests that sufficiently test added/changed functionality
* Relevant documentation change needs to be submitted to keycloak/keycloak-documentation repository
* Should a change be requested in a PR that stays without response for 2 weeks, the PR would be closed

Once you're happy with your changes go to GitHub and create a PR to the master branch.

Expand Down

0 comments on commit afb4a59

Please sign in to comment.