Skip to content

Commit 70c1e81

Browse files
jjchavannejjchavanne
committed
Initial commit
0 parents  commit 70c1e81

File tree

4 files changed

+110
-0
lines changed

4 files changed

+110
-0
lines changed

‎CONTRIBUTING.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
# How to contribute
2+
3+
:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
4+
5+
It's people like you that make security open source such a force in preventing
6+
successful cyber-attacks. Following these guidelines helps keep the project
7+
maintainable, easy to contribute to, and more secure. Thank you for taking the
8+
time to follow this guide.
9+
10+
## Where to start
11+
12+
There are many ways to contribute. You can fix a bug, improve the documentation,
13+
submit bug reports and feature requests, or take a first shot at a feature you
14+
need for yourself.
15+
16+
Pull requests are necessary for all contributions of code or documentation.
17+
18+
## New to open source?
19+
20+
If you're **new to open source** and not sure what a pull request is, welcome!!
21+
We're glad to have you! All of us once had a contribution to make and didn't
22+
know where to start.
23+
24+
Even if you don't write code for your job, don't worry, the skills you learn
25+
during your first contribution to open source can be applied in so many ways,
26+
you'll wonder what you ever did before you had this knowledge. It's worth
27+
learning.
28+
29+
[Learn how to make a pull request](https://github.com/PaloAltoNetworks/.github/blob/master/Learn-GitHub.md#learn-how-to-make-a-pull-request)
30+
31+
## Fixing a typo, or a one or two line fix
32+
33+
Many fixes require little effort or review, such as:
34+
35+
> - Spelling / grammar, typos, white space and formatting changes
36+
> - Comment clean up
37+
> - Change logging messages or debugging output
38+
39+
These small changes can be made directly in GitHub if you like.
40+
41+
Click the pencil icon in GitHub above the file to edit the file directly in
42+
GitHub. This will automatically create a fork and pull request with the change.
43+
See:
44+
[Make a small change with a Pull Request](https://www.freecodecamp.org/news/how-to-make-your-first-pull-request-on-github/)
45+
46+
## Bug fixes and features
47+
48+
For something that is bigger than a one or two line fix, go through the process
49+
of making a fork and pull request yourself:
50+
51+
> 1. Create your own fork of the code
52+
> 2. Clone the fork locally
53+
> 3. Make the changes in your local clone
54+
> 4. Push the changes from local to your fork
55+
> 5. Create a pull request to pull the changes from your fork back into the
56+
> upstream repository
57+
58+
Please use clear commit messages so we can understand what each commit does.
59+
We'll review every PR and might offer feedback or request changes before
60+
merging.

‎LICENSE

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
ISC License
2+
3+
Copyright (c) 2020, Palo Alto Networks Inc.
4+
5+
Permission to use, copy, modify, and/or distribute this software for any
6+
purpose with or without fee is hereby granted, provided that the above
7+
copyright notice and this permission notice appear in all copies.
8+
9+
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
10+
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
11+
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12+
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
13+
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14+
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15+
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

‎README.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# pcs-opensource
2+
Template for all Prisma Cloud open source projects
3+
4+
[![license](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE) [![support](https://img.shields.io/badge/Support%20Level-Community-yellowgreen)](./SUPPORT.md)
5+
6+
## Description
7+
An outline about your project and overview of use.
8+
9+
### Example Formatting
10+
* How bullet things
11+
* Step-by-step bullets
12+
```
13+
code blocks for commands
14+
```
15+
Can also do `inline code` for more specifics
16+
17+
### More examples
18+
1. Numbered list
19+
1. Like so
20+
1. More info
21+
22+
23+
## Version History
24+
25+
* 0.2
26+
* Various changes
27+
* 0.1
28+
* Initial Release
29+
30+
## License
31+
This project is licensed under the MIT License - see the [LICENSE](./LICENSE) file for details

‎SUPPORT.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Community Supported
2+
This template/solution is released under an as-is, best effort, support policy. These scripts should be seen as community supported and Palo Alto Networks will contribute our expertise as and when possible. We do not provide technical support or help in using or troubleshooting the components of the project through our normal support options such as Palo Alto Networks support teams, or ASC (Authorized Support Centers) partners and backline support options. The underlying product used (Prisma Cloud) by the scripts or templates are still supported, but the support is only for the product functionality and not for help in deploying or using the template or script itself.
3+
4+
Unless explicitly tagged, all projects or work posted in our GitHub repository (at https://github.com/PaloAltoNetworks) or sites other than our official Downloads page on https://support.paloaltonetworks.com are provided under the best effort policy.

0 commit comments

Comments
 (0)