Skip to content

Commit 687ab6a

Browse files
Merge pull request #248 from JulianHayward/developmentJH
security & contribution guide
2 parents d17e405 + 74edc49 commit 687ab6a

File tree

2 files changed

+25
-13
lines changed

2 files changed

+25
-13
lines changed

SECURITY.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,22 @@
11
# Security Policy
22

3+
This document outlines security procedures for the Azure Governance Visualizer (aka AzGovViz) project.
4+
5+
We appreciate your dedication to responsible disclosure and will make every effort to acknowledge your contributions.
6+
37
## Supported Versions
48

59
Latest
610

711
## Reporting a Vulnerability
812

9-
Please report (suspected) security vulnerabilities via LinkedIn PN.
10-
If the issue is confirmed, we will release a patch as soon
11-
as possible depending on complexity.
13+
We ask that all suspected vulnerabilities be privately and responsibly disclosed via [LinkedIn PN](https://www.linkedin.com/in/julianhayward/).
14+
15+
Here are some helpful details to include in your report:
16+
17+
- a detailed description of the issue
18+
- the steps required to reproduce the issue
19+
- versions of the project that may be affected by the issue
20+
- if known, any mitigations for the issue
21+
22+
If the issue is confirmed, we will release a patch as soon as possible likely within 1 day to 30 days depending on complexity.

contributionGuide.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,19 @@
11
# Contribution guide
22

33
1. Fork the repository.
4-
1. Change you working directory to `.\Azure-MG-Sub-Governance-Reporting`.
5-
1. In the folder `.\pwsh\dev` find the function you intend to work on and apply your changes.
6-
1. Edit the file `.\pwsh\dev\devAzGovVizParallel.ps1`.
4+
2. Create a branch.
5+
3. Change you working directory to `.\Azure-MG-Sub-Governance-Reporting`.
6+
4. In the folder `.\pwsh\dev` find the function you intend to work on and apply your changes.
7+
5. Edit the file `.\pwsh\dev\devAzGovVizParallel.ps1`.
78
- In the param block update the parameter variable `$ProductVersion` accordingly.
89
- Note: Do not change anything else in this file if you did not introduce new functions!
9-
1. Execute `.\pwsh\dev\buildAzGovVizParallel.ps1` - This step will rebuilt the main `.\pwsh\AzGovVizParallel.ps1` file, incorporating all changes you did in the `.\pwsh\dev` directory.
10-
1. Edit the file `.\README.md`.
10+
6. Execute `.\pwsh\dev\buildAzGovVizParallel.ps1` - This step will rebuild the main `.\pwsh\AzGovVizParallel.ps1` file, incorporating all changes you did in the `.\pwsh\dev` directory.
11+
7. Edit the file `.\README.md`.
1112
- Update the region `Release history`, replace the changes from the previous release with your changes.
12-
1. Edit the file `.\history.md`.
13+
8. Edit the file `.\history.md`.
1314
- Copy over text for the change description you just did for the `.\README.md`.
14-
1. Execute the newly created AzGovViz version to test if it completes successfully by running `.\pwsh\AzGovVizParallel.ps1 -ShowRunIdentifier`.
15+
9. Execute the newly created AzGovViz version to test if it completes successfully by running `.\pwsh\AzGovVizParallel.ps1 -ShowRunIdentifier`.
1516
- From the very last line of the output copy the __run identifier__, you'll need that when you open your pull request.
16-
1. Commit your changes.
17-
1. Create a pull request
18-
- Provide the __run identifier__ in the pull request as a proof of successful test
17+
10. Commit your changes.
18+
11. Create a pull request.
19+
- Provide the __run identifier__ in the pull request as a proof of successful test.

0 commit comments

Comments
 (0)