init repo

This commit is contained in:
Damien Retzinger
2022-06-25 09:59:11 -04:00
commit a6400eb9ec
8 changed files with 302 additions and 0 deletions
+66
View File
@@ -0,0 +1,66 @@
# $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
# $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
# $$ Magento 2 GitHub Actions Code Owners $$
# $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
# $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
#
# The configuration for Code Owners for graycoreio/magento2-github-actions.
#
# For more info see: https://help.github.com/articles/about-codeowners/
#
# ================================================
# Concepts
# ================================================
#
# 1. A CodeOwner should only review what they are comfortable reviewing. If you're not comfortable, say something.
# 2. It is a CodeOwners responsibility to only accept the changes that they understand and deem necessary.
# 3. The CodeOwners have final say on whether or not code is accepted.
# 4. If multiple CodeOwners are listed, ALL code owners must approve the PR prior to merge.
# 5. CodeOwners work in conjunction with Github's "Number of Required Approvals (1)" requirement.
# ================================================
# GitHub username registry
# ================================================
# damienwebdev - Damien Retzinger
######################################################################################################
#
# Team structure and memberships
# ------------------------------
#
#
# Any changes to team structure or memberships must first be made in this file and only then
# implemented in the GitHub UI.
#######################################################################################################
######################################################################################################
#
# CODEOWNERS rules
# -----------------
#
# All the following rules are applied in the order specified in this file.
# The last rule that matches wins!
#
# See https://git-scm.com/docs/gitignore#_pattern_format for pattern syntax docs.
#
######################################################################################################
# ================================================
# Default Owners
# ================================================
* @damienwebdev
# ================================================
# CODEOWNERS Owners owners ...
# ================================================
/.github/CODEOWNERS @damienwebdev
+3
View File
@@ -0,0 +1,3 @@
# These are supported funding model platforms
github: graycoreio
+42
View File
@@ -0,0 +1,42 @@
---
name: Bug report or Regression
about: Create a report to help us fix an issue or regression
title: '[BUG]'
labels: 'bug'
assignees: 'damienwebdev'
---
<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
# :bug: Bug report
## Current Behavior
<!-- Describe how the issue manifests. -->
## Expected Behavior
<!-- Describe what the expected behavior is. -->
## Minimal reproduction of the problem with instructions
<!-- Please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem -->
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
## Environment
<pre><code>
Magento version: X.Y.Z
PHP Version version: X.Y.Z
<!-- Check whether this is still an issue in the most recent magento2-cors version -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
+37
View File
@@ -0,0 +1,37 @@
---
name: Documentation Request
about: Request additional documentation or clarification on a feature.
title: '[DOCS]'
labels: 'docs'
assignees: 'damienwebdev'
---
<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
# :page_facing_up: Documentation Request
## What were you doing?
<!-- Describe how you came to need the documentation. -->
## Expected behavior
<!-- Describe not only **what** you would like to see documented, but also **where** you'd like to see it. -->
## Existing Documentation
<!-- Describe any existing documentation that would potentially require change. -->
## Environment
<pre><code>
Magento version: X.Y.Z
PHP Version version: X.Y.Z
<!-- Check whether this is still an issue in the most recent magento2-cors version -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
+42
View File
@@ -0,0 +1,42 @@
---
name: Feature Request
about: Ask for a new feature, or something that you'd like to see changed.
title: '[FEAT]'
labels: 'feat'
assignees: 'damienwebdev'
---
<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
# :bulb: Feature request
## Feature Name
<!-- Naming is hard, what do YOU call this feature? -->
## The Desired Behavior
<!-- Please describe, in as much detail as you can, what you'd like to see happen. -->
## Your Use Case
<!-- Please try to format as "As a {role}, I'd like to be able to do {x}. -->
## Prior Work
<!-- If you got this idea from somewhere, please indicate where you got it from. -->
## Environment
<pre><code>
Magento version: X.Y.Z
PHP Version version: X.Y.Z
<!-- Check whether this is still an issue in the most recent magento2-cors version -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
+28
View File
@@ -0,0 +1,28 @@
---
name: Other
about: Report a general issue that isn't covered by other issue templates.
title: '[OTHER]'
labels: ''
assignees: ''
---
<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
# :question: Other
<!-- If you're asking a question, have you searched through Github first? -->
## Environment
<pre><code>
Magento version: X.Y.Z
PHP Version version: X.Y.Z
<!-- Check whether this is still an issue in the most recent magento2-cors version -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
@@ -0,0 +1,42 @@
---
name: Performance Issue
about: Create a report about a performance problem.
title: '[PERF]'
labels: 'perf'
assignees: 'damienwebdev'
---
<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
# :turtle: Performance Issue
## Current behavior
<!-- Describe how the issue manifests. -->
## Expected behavior
<!-- Describe what the expected behavior is. -->
## Minimal reproduction of the problem with instructions
<!-- Please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem -->
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
## Environment
<pre><code>
Magento version: X.Y.Z
PHP Version version: X.Y.Z
<!-- Check whether this is still an issue in the most recent magento2-cors version -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
+42
View File
@@ -0,0 +1,42 @@
## PR Checklist
Please check if your PR fulfills the following requirements:
- [ ] The commit message follows our guidelines: https://github.com/graycoreio/magento2-github-actions/blob/master/CONTRIBUTING.md#commit
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)
## PR Type
What kind of change does this PR introduce?
<!-- Please check the one that applies to this PR using "x". -->
```
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
```
## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Fixes: N/A
## What is the new behavior?
## Does this PR introduce a breaking change?
```
[ ] Yes
[ ] No
```
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
## Other information