Commit 4ff157d4 authored by Dmitriy Zaporozhets's avatar Dmitriy Zaporozhets

Merge branch 'security_vulnerabilities' of /home/git/repositories/gitlab/gitlabhq

parents 4a715c73 8706890f
...@@ -5,6 +5,7 @@ This guide details how to use issues and pull requests to improve GitLab. ...@@ -5,6 +5,7 @@ This guide details how to use issues and pull requests to improve GitLab.
- [Closing policy for issues and pull requests](#closing-policy-for-issues-and-pull-requests) - [Closing policy for issues and pull requests](#closing-policy-for-issues-and-pull-requests)
- [Issue tracker](#issue-tracker) - [Issue tracker](#issue-tracker)
- [Pull requests](#pull-requests) - [Pull requests](#pull-requests)
- [Security vulnerabilities](#security-vulnerabilities)
If you want to know how the GitLab team handles contributions have a look at [the GitLab contributing process](PROCESS.md). If you want to know how the GitLab team handles contributions have a look at [the GitLab contributing process](PROCESS.md).
...@@ -73,3 +74,6 @@ We will accept pull requests if: ...@@ -73,3 +74,6 @@ We will accept pull requests if:
* It is a single commit (please use `git rebase -i` to squash commits) * It is a single commit (please use `git rebase -i` to squash commits)
For examples of feedback on pull requests please look at already [closed pull requests](https://github.com/gitlabhq/gitlabhq/pulls?direction=desc&page=1&sort=created&state=closed). For examples of feedback on pull requests please look at already [closed pull requests](https://github.com/gitlabhq/gitlabhq/pulls?direction=desc&page=1&sort=created&state=closed).
## Security vulnerabilities
Please report security vulnerabilities in private to support@gitlab.com; also see http://www.gitlab.com/disclosure/. Do NOT create GitHub issues for security vulnerabilities.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment