forked from google/perfetto
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve Perfetto Fork PR Template (#102)
- Loading branch information
1 parent
9407d38
commit 4ec0ec7
Showing
1 changed file
with
19 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,21 @@ | ||
Please do not submit a Pull Request via GitHub. | ||
Our project makes use of Gerrit for patch submission and review. | ||
<!-- | ||
Thank you for your Pull Request. Please provide a description and review the requirements below. | ||
For more details please see | ||
https://perfetto.dev/docs/contributing/getting-started | ||
*** | ||
Please make sure that you set 'eclipsesource/perfetto' as the base repository with 'reuse_timeline' as base branch for this pull request. By default, GitHub uses the upstream repository from Google as base repository but in 99% of the cases you'll want your contribution to go into this fork. | ||
*** | ||
If you have discovered a security vulnerability in this project, please report it privately. Do not disclose it as a public issue. This gives us time to work with you to fix the issue before public exposure, reducing the chance that the exploit will be used before a patch is released. Please disclose it at https://github.com/eclipsesource/perfetto/security/advisories/new. | ||
--> | ||
|
||
#### What it does | ||
|
||
<!-- Include relevant issues and describe how they are addressed. --> | ||
|
||
#### How to test | ||
|
||
<!-- Explain how a reviewer can reproduce a bug, test new functionality or verify performance improvements. --> | ||
|
||
#### Follow-ups | ||
|
||
<!-- Please list potential follow-up work, including known issues, possible future work, identified technical debt, and potentially introduced technical debt. If the PR introduces technical debt, specify the reason why this is acceptable. Please create tickets and link them here. Please use the label "technical debt" for new issues when it applies. --> |