Merge pull request #4 from sanidhyy/docs/add-missing-contact-email
docs: add missing community contact email
This commit is contained in:
+1
-1
@@ -56,7 +56,7 @@ representative at an online or offline event.
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported to the community leaders responsible for enforcement at .
|
||||
reported to the community leaders responsible for enforcement at <sanidhyyy@gmail.com>.
|
||||
All complaints will be reviewed and investigated promptly and fairly.
|
||||
|
||||
All community leaders are obligated to respect the privacy and security of the
|
||||
|
||||
+2
-2
@@ -31,7 +31,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents
|
||||
This project and everyone participating in it is governed by the
|
||||
[Ryde Code of Conduct](https://github.com/sanidhyy/uber-cloneblob/master/CODE_OF_CONDUCT.md).
|
||||
By participating, you are expected to uphold this code. Please report unacceptable behavior
|
||||
to .
|
||||
to <sanidhyyy@gmail.com>.
|
||||
|
||||
|
||||
## I Have a Question
|
||||
@@ -74,7 +74,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
|
||||
<!-- omit in toc -->
|
||||
#### How Do I Submit a Good Bug Report?
|
||||
|
||||
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to .
|
||||
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <sanidhyyy@gmail.com>.
|
||||
|
||||
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
|
||||
|
||||
|
||||
+5
-13
@@ -2,20 +2,12 @@
|
||||
|
||||
## Supported Versions
|
||||
|
||||
Use this section to tell people about which versions of your project are
|
||||
currently being supported with security updates.
|
||||
|
||||
| Version | Supported |
|
||||
| ------- | ------------------ |
|
||||
| 5.1.x | :white_check_mark: |
|
||||
| 5.0.x | :x: |
|
||||
| 4.0.x | :white_check_mark: |
|
||||
| < 4.0 | :x: |
|
||||
This project is maintained on the default branch. Please use the latest commit when reporting issues.
|
||||
|
||||
## Reporting a Vulnerability
|
||||
|
||||
Use this section to tell people how to report a vulnerability.
|
||||
Report security vulnerabilities privately to <sanidhyyy@gmail.com>.
|
||||
Please do not open a public GitHub issue for security reports.
|
||||
|
||||
Tell them where to go, how often they can expect to get an update on a
|
||||
reported vulnerability, what to expect if the vulnerability is accepted or
|
||||
declined, etc.
|
||||
Reports will be reviewed as soon as possible. If a report is accepted, we will work on a fix.
|
||||
If it is declined, we will explain why.
|
||||
|
||||
Reference in New Issue
Block a user