Skip to content

Commit

Permalink
Initial 2.0.0 changes
Browse files Browse the repository at this point in the history
  • Loading branch information
Celerium committed Oct 29, 2023
1 parent b8c2bbb commit 3e11e42
Show file tree
Hide file tree
Showing 221 changed files with 45,184 additions and 3,669 deletions.
4 changes: 1 addition & 3 deletions .github/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,4 @@ members of the project's leadership.

## Attribution

> This Code of Conduct is adapted from the [Probot](https://github.com/probot/template/blob/master/CODE_OF_CONDUCT.md) Code of Conduct.
> Which was adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html) Code of Conduct.
> This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html) Code of Conduct.
16 changes: 4 additions & 12 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,19 +4,14 @@
## **Did you find a bug?**

* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/Celerium/MyITProcess-PowerShellWrapper/issues).
* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/Celerium/MyITProcessAPI/issues).

* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/Celerium/MyITProcess-PowerShellWrapper/issues/new/choose).
* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/Celerium/MyITProcessAPI/issues/new/choose).
* Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.

## **Did you write a patch that fixes a bug?**

* [ ] Submit a pulling request to the **development** branch
* [ ] Ensure the pull request description clearly describes the problem and solution.
* [ ] Make sure the **ModuleVersion** number is updated in the **MyITProcessAPI.psd1** file
* MAJOR version when you make incompatible API changes,
* MINOR version when you add functionality in a backwards-compatible manner, and
* PATCH version when you make backwards-compatible bug fixes.

If the feature is accepted and I have time to test, the pull request will be approved.

Expand All @@ -28,15 +23,12 @@ If the feature is accepted and I have time to test, the pull request will be app

* Once the new feature is ready,

- [ ] Make sure the ModuleManifest "ModuleVersion" number is updated
- [ ] Update any documentation if needed
- [ ] Submit a pulling request to the **development** branch

* [ ] Update any documentation if needed

If the feature is accepted and I have time to test, the pull request will be approved.

Thanks! :heart:

---

> Based off of the Ruby on Rails project [contribution guide](https://github.com/rails/rails/blob/master/CONTRIBUTING.md).
> Based off of the Ruby on Rails project [contribution guide](https://github.com/rails/rails/blob/master/CONTRIBUTING.md).
Binary file removed .github/Celerium-MyITProcess.png
Binary file not shown.
2 changes: 1 addition & 1 deletion .github/FUNDING.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# These are supported funding model platforms

custom: 'https://paypal.me/CeleriumSupport'
custom: 'https://www.buymeacoffee.com/Celerium'
88 changes: 88 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
name: 🐛 Bug Report
description: File a bug report to help us improve
title: "[Bug]: "
labels: ["type: bug"]
assignees:
- Celerium
body:
- type: markdown
attributes:
value: |
Thank you for taking the time to fill out this bug report!
- type: textarea
id: what-happened
attributes:
label: What happened?
placeholder: Tell us what you see!
value: "A bug happened!"
validations:
required: true
- type: textarea
id: ExpectedBehavior
attributes:
label: Expected behavior?
placeholder: Tell us what you see!
value: "A bug shouldn't have happened!"
validations:
required: true
- type: textarea
id: PossibleSolution
attributes:
label: Possible Solution?
validations:
required: false
- type: dropdown
id: PowerShellVersion
attributes:
label: PowerShell Version
description: What version of PowerShell are you running?
options:
- 5.1 - (PowerShell)
- 7.2.x - (PowerShell Core)
- 7.3.x - (PowerShell Core)
- 7.4.x - (PowerShell Core)
- type: dropdown
id: OperatingSystem
attributes:
label: What operating system are you seeing the problem on?
multiple: true
options:
- Windows
- Linux - Ubuntu\Debian
- Linux - CentOS\RedHat\Fedora
- Linux - openSUSE
- macOS
- type: textarea
id: logs
attributes:
label: Relevant log output
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
render: PowerShell
- type: textarea
id: HelpCommands
attributes:
label: Help Commands
description: Please share additional details about your environment.
value: "$PSversionTable
Get-Package -Name xxxModuleNamexxx | Select-Object Name,Version,Source,ProviderName
Get-ComputerInfo -Property @(
'OsName',
'OsVersion',
'OsOperatingSystemSKU',
'OSArchitecture',
'WindowsVersion',
'WindowsBuildLabEx',
'OsLanguage',
'OsMuiLanguages'
)"
render: PowerShell
- type: checkboxes
id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Celerium/MyITProcessAPI/blob/main/.github/CODE_OF_CONDUCT.md)
options:
- label: I agree to follow this project's Code of Conduct
required: true
11 changes: 11 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
blank_issues_enabled: true
contact_links:
- name: Project Documentation
url: https://celerium.github.io/MyITProcessAPI/
about: Read through the generated documentation
- name: Vendor Documentation
url: https://github.com/Celerium
about: Read through the vendors documentation
- name: Celerium.org
url: https://celerium.org
about: Website were I publish more information related to this project.
40 changes: 40 additions & 0 deletions .github/ISSUE_TEMPLATE/documentation_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
name: 📝 Documentation Request
description: Suggest extra documentation for this project
title: "[Documentation Request]: "
labels: ["type: documentation"]
assignees:
- Celerium
body:
- type: checkboxes
id: ReadME
attributes:
label: Project README
description: "[Project README](https://github.com/Celerium/xxxREPONAMExxx/blob/main/README.md)"
options:
- label: "Have you read the projects README?"
- type: checkboxes
id: WebDocumentation
attributes:
label: Online Documentation
description: "[Online Documentation](https://Celerium.github.io/xxxREPONAMExxx/)"
options:
- label: "Have you read the online documentation"
- type: checkboxes
id: PowerShellHelp
attributes:
label: PowerShell Help
description: "Get-Help Get-xxxModulePrefixxxx<RESOURCES-NAME> -Full"
options:
- label: "Have you read the help output?"
- type: textarea
id: DocumentationRequest
attributes:
label: Documentation Request
description: What would you like to see more documentation around?
render: Text
- type: textarea
id: ExistingIssue
attributes:
label: Existing Issue?
description: Is this related to an existing issue? If so please describe or link.
value: "Issue: #12345"
46 changes: 46 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
name: 🚀 Feature Request
description: Suggest a new feature for this project
title: "[Feature Request]: "
labels: ["type: feature request"]
assignees:
- Celerium
body:
- type: checkboxes
id: ReadME
attributes:
label: Project README
description: "[Project README](https://github.com/Celerium/xxxREPONAMExxx/blob/main/README.md)"
options:
- label: "Have you read the projects README?"
- type: checkboxes
id: WebDocumentation
attributes:
label: Online Documentation
description: "[Online Documentation](https://Celerium.github.io/xxxREPONAMExxx/)"
options:
- label: "Have you read the online documentation"
- type: checkboxes
id: PowerShellHelp
attributes:
label: PowerShell Help
description: "Get-Help Get-xxxModulePrefixxxx<RESOURCES-NAME> -Full"
options:
- label: "Have you read the help output?"
- type: textarea
id: NewFeature
attributes:
label: Describe the solution you'd like
description: A clear and concise description of what you want to happen.
render: Text
- type: textarea
id: NewFeatureAlternatives
attributes:
label: Describe alternatives you've considered
description: A clear and concise description of any alternative solutions or features you've considered.
render: Text
- type: textarea
id: ExistingIssue
attributes:
label: Existing Issue?
description: Is this related to an existing issue? If so please describe or link.
value: "Issue: #12345"
40 changes: 40 additions & 0 deletions .github/ISSUE_TEMPLATE/help_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
name: 👋 Help Request
description: What can the community help with
title: "[Help Request]: "
labels: ["help wanted"]
assignees:
- Celerium
body:
- type: checkboxes
id: ReadME
attributes:
label: Project README
description: "[Project README](https://github.com/Celerium/xxxREPONAMExxx/blob/main/README.md)"
options:
- label: "Have you read the projects README?"
- type: checkboxes
id: WebDocumentation
attributes:
label: Online Documentation
description: "[Online Documentation](https://Celerium.github.io/xxxREPONAMExxx/)"
options:
- label: "Have you read the online documentation"
- type: checkboxes
id: PowerShellHelp
attributes:
label: PowerShell Help
description: "Get-Help Get-xxxModulePrefixxxx<RESOURCES-NAME> -Full"
options:
- label: "Have you read the help output?"
- type: textarea
id: HelpRequest
attributes:
label: Help Request
description: What would you like help with?
render: Text
- type: textarea
id: ExistingIssue
attributes:
label: Existing Issue?
description: Is this related to an existing issue? If so please describe or link.
value: "Issue: #12345"
32 changes: 32 additions & 0 deletions .github/SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Responsible Security Disclosure README standard

## Our security policy and Your responsibility

- **POLICY**:

*Our security policy is to avoid leaving the ecosystem worse than we found it. Meaning we are not planning to introduce vulnerabilities into the ecosystem.*

The "MyITProcessAPI" team and community take all security bugs in "MyITProcessAPI" seriously. Thank you for improving the security of "MyITProcessAPI". We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.

Report security bugs by emailing the lead maintainer at [celerium@celerium.org] and include the word "SECURITY" in the subject line..

The lead maintainer will acknowledge your email within a week, and will send a more detailed response 48 hours after that indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

- "MyITProcessAPI" will confirm the problem and determine the affected versions.
- "MyITProcessAPI" will audit code to find any potential similar problems.
- "MyITProcessAPI" will prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible.

Report security bugs in third-party modules to the person or team maintaining the module.

- **SECURITY DISCLOSURE**:

*Your responsibility is to report vulnerabilities to us using the guidelines outlined below.*

Discuss how someone should disclose a vulnerability to "MyITProcessAPI", in tl;dr ( or ELI5 ) language. Then expand on this with "How To Disclose a vulnerability in detail". Please give detailed steps on how to disclose the vulnerability. Keep these OWASP guidelines in mind ( <https://www.owasp.org/index.php/Vulnerability_Disclosure_Cheat_Sheet> ) when creating your disclosure policy. Below are some recommendations for security disclosures:

- "MyITProcessAPI" security contact { contact: mailto:[celerium@celerium.org] }
- Disclosure format: When disclosing vulnerabilities please
1. Your name and affiliation (if any).
2. include scope of vulnerability. Let us know who could use this exploit.
3. document steps to identify the vulnerability. It is important that we can reproduce your findings.
4. how to exploit vulnerability, give us an attack scenario.
Loading

0 comments on commit 3e11e42

Please sign in to comment.