Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
80 changes: 40 additions & 40 deletions .github/ISSUE_TEMPLATE/bug-report---deployed-functionality.md
Original file line number Diff line number Diff line change
@@ -1,40 +1,40 @@
---
name: Bug report - Deployed Functionality
about: Used to report bugs with the environment deployment by the Accelerator
title: "[BUG][Functional] Meaningful bug description"
labels: bug
assignees: Brian969
---
Bug reports which fail to provide the required information will be closed without action.
**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)
**Describe the bug**
(A clear and concise description of what the bug is.)
**Failure Info**
- What error messages have you identified, if any:
- What symptoms have you identified, if any:
**Required files**
- Please provide a copy of your config.json file (sanitize if required)
**Steps To Reproduce**
1. Go to '...'
2. Click on '....'
3. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Add any other context about the problem here.
---
name: Bug report - Deployed Functionality
about: Used to report bugs with the environment deployment by the Accelerator
title: "[BUG][Functional] Meaningful bug description"
labels: bug
assignees: Brian969

---

Bug reports which fail to provide the required information will be closed without action.

**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)

**Describe the bug**
(A clear and concise description of what the bug is.)

**Failure Info**
- What error messages have you identified, if any:
- What symptoms have you identified, if any:

**Required files**
- Please provide a copy of your config.json file (sanitize if required)

**Steps To Reproduce**
1. Go to '...'
2. Click on '....'
3. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Additional context**
Add any other context about the problem here.
50 changes: 25 additions & 25 deletions .github/ISSUE_TEMPLATE/bug-report---documentation.md
Original file line number Diff line number Diff line change
@@ -1,25 +1,25 @@
---
name: Bug report - Documentation
about: Used to report documentation errors
title: "[BUG][DOCS] Meaningful bug description"
labels: documentation
assignees: Brian969
---
Bug reports which fail to provide the required information will be closed without action.
**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Document filename: (eg. /docs/installation/index.md)
**Describe the bug**
(A clear and concise description as to the concern or problem with the documentation)
**Expected update**
If you have a desired outcome, please provide details as to suggested updates
**Additional context**
Add any other context about the problem here.
---
name: Bug report - Documentation
about: Used to report documentation errors
title: "[BUG][DOCS] Meaningful bug description"
labels: documentation
assignees: Brian969

---

Bug reports which fail to provide the required information will be closed without action.

**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Document filename: (eg. /docs/installation/index.md)

**Describe the bug**
(A clear and concise description as to the concern or problem with the documentation)

**Expected update**
If you have a desired outcome, please provide details as to suggested updates

**Additional context**
Add any other context about the problem here.
96 changes: 48 additions & 48 deletions .github/ISSUE_TEMPLATE/bug-report---other.md
Original file line number Diff line number Diff line change
@@ -1,48 +1,48 @@
---
name: Bug report - Other
about: Used to report bugs not covered by a specific bug category
title: "[BUG][OTHER] Meaningful bug description"
labels: bug
assignees: Brian969
---
Bug reports which fail to provide the required information will be closed without action.
**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)
- Which State did the Main State Machine Fail in: (e.g. N/A, Phase 0)
**INTERNAL ONLY - TEMPORARY**
- please place the account in a group named Accel-Issue
- please provide bmycroft@ access to your internal failed master AWS account
**Describe the bug**
(A clear and concise description of what the bug is.)
**Failure Info**
- What error messages have you identified, if any:
- What symptoms have you identified, if any:
**Required files**
- Please provide a copy of your config.json file (sanitize if required)
- If a CodeBuild step failed- please provide the full CodeBuild Log
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
- In many cases it would be helpful if you went into the failed sub-account and region, CloudFormation, and provided a screenshot of the Events section of the failed, deleted, or rolled back stack including the last successful item, including the first couple of error messages (bottom up)
**Steps To Reproduce**
1. Go to '...'
2. Click on '....'
3. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Add any other context about the problem here.
---
name: Bug report - Other
about: Used to report bugs not covered by a specific bug category
title: "[BUG][OTHER] Meaningful bug description"
labels: bug
assignees: Brian969

---

Bug reports which fail to provide the required information will be closed without action.

**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)
- Which State did the Main State Machine Fail in: (e.g. N/A, Phase 0)

**INTERNAL ONLY - TEMPORARY**
- please place the account in a group named Accel-Issue
- please provide bmycroft@ access to your internal failed master AWS account

**Describe the bug**
(A clear and concise description of what the bug is.)

**Failure Info**
- What error messages have you identified, if any:
- What symptoms have you identified, if any:

**Required files**
- Please provide a copy of your config.json file (sanitize if required)
- If a CodeBuild step failed- please provide the full CodeBuild Log
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
- In many cases it would be helpful if you went into the failed sub-account and region, CloudFormation, and provided a screenshot of the Events section of the failed, deleted, or rolled back stack including the last successful item, including the first couple of error messages (bottom up)

**Steps To Reproduce**
1. Go to '...'
2. Click on '....'
3. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Additional context**
Add any other context about the problem here.
88 changes: 44 additions & 44 deletions .github/ISSUE_TEMPLATE/bug-report---state-machine-failure.md
Original file line number Diff line number Diff line change
@@ -1,44 +1,44 @@
---
name: Bug report - State Machine Failure
about: Use to report bugs related to state machine failures
title: "[BUG] [SM] Meaningful bug description"
labels: bug
assignees: Brian969
---
Bug reports which fail to provide the required information will be closed without action.
**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)
- Which State did the Main State Machine Fail in: (e.g. Phase 0)
**Describe the bug**
(A clear and concise description of what the bug is.)
**Failure Info**
- What error messages have you identified, if any:
- What symptoms have you identified, if any:
**Required files**
- Please provide a copy of your config.json file (sanitize if required)
- If a CodeBuild step failed- please provide the full CodeBuild Log
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
- In many cases it would be helpful if you went into the failed sub-account and region, CloudFormation, and provided a screenshot of the Events section of the failed, deleted, or rolled back stack including the last successful item, including the first couple of error messages (bottom up)
**Steps To Reproduce**
1. Go to '...'
2. Click on '....'
3. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Add any other context about the problem here.
---
name: Bug report - State Machine Failure
about: Use to report bugs related to state machine failures
title: "[BUG] [SM] Meaningful bug description"
labels: bug
assignees: Brian969

---

Bug reports which fail to provide the required information will be closed without action.

**Required Basic Info**
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)
- Which State did the Main State Machine Fail in: (e.g. Phase 0)

**Describe the bug**
(A clear and concise description of what the bug is.)

**Failure Info**
- What error messages have you identified, if any:
- What symptoms have you identified, if any:

**Required files**
- Please provide a copy of your config.json file (sanitize if required)
- If a CodeBuild step failed- please provide the full CodeBuild Log
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
- In many cases it would be helpful if you went into the failed sub-account and region, CloudFormation, and provided a screenshot of the Events section of the failed, deleted, or rolled back stack including the last successful item, including the first couple of error messages (bottom up)

**Steps To Reproduce**
1. Go to '...'
2. Click on '....'
3. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Additional context**
Add any other context about the problem here.
54 changes: 27 additions & 27 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -1,27 +1,27 @@
---
name: Feature request
about: Suggest an idea for enhancements to the Accelerator
title: "[FEATURE] Meaningful enhancement description"
labels: enhancement
assignees: Brian969
---
**Required Basic Info**
To properly assess the enhancement request, we require information on the version of the Accelerator you based this request upon:
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
---
name: Feature request
about: Suggest an idea for enhancements to the Accelerator
title: "[FEATURE] Meaningful enhancement description"
labels: enhancement
assignees: Brian969

---

**Required Basic Info**
To properly assess the enhancement request, we require information on the version of the Accelerator you based this request upon:
- Accelerator Version: (eg. v1.1.6)
- Install Type: (Clean or Upgrade)
- Install Branch: (ALZ or Standalone)
- Upgrade from version: (N/A or v1.x.y)

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
2 changes: 1 addition & 1 deletion .github/PULL_REQUEST_TEMPLATE
Original file line number Diff line number Diff line change
@@ -1 +1 @@
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Loading