Skip to content

Commit 12523d7

Browse files
dliggatdliggat
authored
Run dos2unix recursively on all files (#341)
1 parent d4f5fb3 commit 12523d7

File tree

367 files changed

+31826
-31826
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

367 files changed

+31826
-31826
lines changed

‎.github/ISSUE_TEMPLATE/bug-report---deployed-functionality.md‎

Lines changed: 40 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,40 @@
1-
---
2-
name: Bug report - Deployed Functionality
3-
about: Used to report bugs with the environment deployment by the Accelerator
4-
title: "[BUG][Functional] Meaningful bug description"
5-
labels: bug
6-
assignees: Brian969
7-
8-
---
9-
10-
Bug reports which fail to provide the required information will be closed without action.
11-
12-
**Required Basic Info**
13-
- Accelerator Version: (eg. v1.1.6)
14-
- Install Type: (Clean or Upgrade)
15-
- Install Branch: (ALZ or Standalone)
16-
- Upgrade from version: (N/A or v1.x.y)
17-
18-
**Describe the bug**
19-
(A clear and concise description of what the bug is.)
20-
21-
**Failure Info**
22-
- What error messages have you identified, if any:
23-
- What symptoms have you identified, if any:
24-
25-
**Required files**
26-
- Please provide a copy of your config.json file (sanitize if required)
27-
28-
**Steps To Reproduce**
29-
1. Go to '...'
30-
2. Click on '....'
31-
3. See error
32-
33-
**Expected behavior**
34-
A clear and concise description of what you expected to happen.
35-
36-
**Screenshots**
37-
If applicable, add screenshots to help explain your problem.
38-
39-
**Additional context**
40-
Add any other context about the problem here.
1+
---
2+
name: Bug report - Deployed Functionality
3+
about: Used to report bugs with the environment deployment by the Accelerator
4+
title: "[BUG][Functional] Meaningful bug description"
5+
labels: bug
6+
assignees: Brian969
7+
8+
---
9+
10+
Bug reports which fail to provide the required information will be closed without action.
11+
12+
**Required Basic Info**
13+
- Accelerator Version: (eg. v1.1.6)
14+
- Install Type: (Clean or Upgrade)
15+
- Install Branch: (ALZ or Standalone)
16+
- Upgrade from version: (N/A or v1.x.y)
17+
18+
**Describe the bug**
19+
(A clear and concise description of what the bug is.)
20+
21+
**Failure Info**
22+
- What error messages have you identified, if any:
23+
- What symptoms have you identified, if any:
24+
25+
**Required files**
26+
- Please provide a copy of your config.json file (sanitize if required)
27+
28+
**Steps To Reproduce**
29+
1. Go to '...'
30+
2. Click on '....'
31+
3. See error
32+
33+
**Expected behavior**
34+
A clear and concise description of what you expected to happen.
35+
36+
**Screenshots**
37+
If applicable, add screenshots to help explain your problem.
38+
39+
**Additional context**
40+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/bug-report---documentation.md‎

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,25 @@
1-
---
2-
name: Bug report - Documentation
3-
about: Used to report documentation errors
4-
title: "[BUG][DOCS] Meaningful bug description"
5-
labels: documentation
6-
assignees: Brian969
7-
8-
---
9-
10-
Bug reports which fail to provide the required information will be closed without action.
11-
12-
**Required Basic Info**
13-
- Accelerator Version: (eg. v1.1.6)
14-
- Install Type: (Clean or Upgrade)
15-
- Install Branch: (ALZ or Standalone)
16-
- Document filename: (eg. /docs/installation/index.md)
17-
18-
**Describe the bug**
19-
(A clear and concise description as to the concern or problem with the documentation)
20-
21-
**Expected update**
22-
If you have a desired outcome, please provide details as to suggested updates
23-
24-
**Additional context**
25-
Add any other context about the problem here.
1+
---
2+
name: Bug report - Documentation
3+
about: Used to report documentation errors
4+
title: "[BUG][DOCS] Meaningful bug description"
5+
labels: documentation
6+
assignees: Brian969
7+
8+
---
9+
10+
Bug reports which fail to provide the required information will be closed without action.
11+
12+
**Required Basic Info**
13+
- Accelerator Version: (eg. v1.1.6)
14+
- Install Type: (Clean or Upgrade)
15+
- Install Branch: (ALZ or Standalone)
16+
- Document filename: (eg. /docs/installation/index.md)
17+
18+
**Describe the bug**
19+
(A clear and concise description as to the concern or problem with the documentation)
20+
21+
**Expected update**
22+
If you have a desired outcome, please provide details as to suggested updates
23+
24+
**Additional context**
25+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/bug-report---other.md‎

Lines changed: 48 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1,48 @@
1-
---
2-
name: Bug report - Other
3-
about: Used to report bugs not covered by a specific bug category
4-
title: "[BUG][OTHER] Meaningful bug description"
5-
labels: bug
6-
assignees: Brian969
7-
8-
---
9-
10-
Bug reports which fail to provide the required information will be closed without action.
11-
12-
**Required Basic Info**
13-
- Accelerator Version: (eg. v1.1.6)
14-
- Install Type: (Clean or Upgrade)
15-
- Install Branch: (ALZ or Standalone)
16-
- Upgrade from version: (N/A or v1.x.y)
17-
- Which State did the Main State Machine Fail in: (e.g. N/A, Phase 0)
18-
19-
**INTERNAL ONLY - TEMPORARY**
20-
- please place the account in a group named Accel-Issue
21-
- please provide bmycroft@ access to your internal failed master AWS account
22-
23-
**Describe the bug**
24-
(A clear and concise description of what the bug is.)
25-
26-
**Failure Info**
27-
- What error messages have you identified, if any:
28-
- What symptoms have you identified, if any:
29-
30-
**Required files**
31-
- Please provide a copy of your config.json file (sanitize if required)
32-
- If a CodeBuild step failed- please provide the full CodeBuild Log
33-
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
34-
- 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)
35-
36-
**Steps To Reproduce**
37-
1. Go to '...'
38-
2. Click on '....'
39-
3. See error
40-
41-
**Expected behavior**
42-
A clear and concise description of what you expected to happen.
43-
44-
**Screenshots**
45-
If applicable, add screenshots to help explain your problem.
46-
47-
**Additional context**
48-
Add any other context about the problem here.
1+
---
2+
name: Bug report - Other
3+
about: Used to report bugs not covered by a specific bug category
4+
title: "[BUG][OTHER] Meaningful bug description"
5+
labels: bug
6+
assignees: Brian969
7+
8+
---
9+
10+
Bug reports which fail to provide the required information will be closed without action.
11+
12+
**Required Basic Info**
13+
- Accelerator Version: (eg. v1.1.6)
14+
- Install Type: (Clean or Upgrade)
15+
- Install Branch: (ALZ or Standalone)
16+
- Upgrade from version: (N/A or v1.x.y)
17+
- Which State did the Main State Machine Fail in: (e.g. N/A, Phase 0)
18+
19+
**INTERNAL ONLY - TEMPORARY**
20+
- please place the account in a group named Accel-Issue
21+
- please provide bmycroft@ access to your internal failed master AWS account
22+
23+
**Describe the bug**
24+
(A clear and concise description of what the bug is.)
25+
26+
**Failure Info**
27+
- What error messages have you identified, if any:
28+
- What symptoms have you identified, if any:
29+
30+
**Required files**
31+
- Please provide a copy of your config.json file (sanitize if required)
32+
- If a CodeBuild step failed- please provide the full CodeBuild Log
33+
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
34+
- 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)
35+
36+
**Steps To Reproduce**
37+
1. Go to '...'
38+
2. Click on '....'
39+
3. See error
40+
41+
**Expected behavior**
42+
A clear and concise description of what you expected to happen.
43+
44+
**Screenshots**
45+
If applicable, add screenshots to help explain your problem.
46+
47+
**Additional context**
48+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/bug-report---state-machine-failure.md‎

Lines changed: 44 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,44 @@
1-
---
2-
name: Bug report - State Machine Failure
3-
about: Use to report bugs related to state machine failures
4-
title: "[BUG] [SM] Meaningful bug description"
5-
labels: bug
6-
assignees: Brian969
7-
8-
---
9-
10-
Bug reports which fail to provide the required information will be closed without action.
11-
12-
**Required Basic Info**
13-
- Accelerator Version: (eg. v1.1.6)
14-
- Install Type: (Clean or Upgrade)
15-
- Install Branch: (ALZ or Standalone)
16-
- Upgrade from version: (N/A or v1.x.y)
17-
- Which State did the Main State Machine Fail in: (e.g. Phase 0)
18-
19-
**Describe the bug**
20-
(A clear and concise description of what the bug is.)
21-
22-
**Failure Info**
23-
- What error messages have you identified, if any:
24-
- What symptoms have you identified, if any:
25-
26-
**Required files**
27-
- Please provide a copy of your config.json file (sanitize if required)
28-
- If a CodeBuild step failed- please provide the full CodeBuild Log
29-
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
30-
- 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)
31-
32-
**Steps To Reproduce**
33-
1. Go to '...'
34-
2. Click on '....'
35-
3. See error
36-
37-
**Expected behavior**
38-
A clear and concise description of what you expected to happen.
39-
40-
**Screenshots**
41-
If applicable, add screenshots to help explain your problem.
42-
43-
**Additional context**
44-
Add any other context about the problem here.
1+
---
2+
name: Bug report - State Machine Failure
3+
about: Use to report bugs related to state machine failures
4+
title: "[BUG] [SM] Meaningful bug description"
5+
labels: bug
6+
assignees: Brian969
7+
8+
---
9+
10+
Bug reports which fail to provide the required information will be closed without action.
11+
12+
**Required Basic Info**
13+
- Accelerator Version: (eg. v1.1.6)
14+
- Install Type: (Clean or Upgrade)
15+
- Install Branch: (ALZ or Standalone)
16+
- Upgrade from version: (N/A or v1.x.y)
17+
- Which State did the Main State Machine Fail in: (e.g. Phase 0)
18+
19+
**Describe the bug**
20+
(A clear and concise description of what the bug is.)
21+
22+
**Failure Info**
23+
- What error messages have you identified, if any:
24+
- What symptoms have you identified, if any:
25+
26+
**Required files**
27+
- Please provide a copy of your config.json file (sanitize if required)
28+
- If a CodeBuild step failed- please provide the full CodeBuild Log
29+
- If a Lambda step failed - please provide the full Lambda CloudWatch Log
30+
- 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)
31+
32+
**Steps To Reproduce**
33+
1. Go to '...'
34+
2. Click on '....'
35+
3. See error
36+
37+
**Expected behavior**
38+
A clear and concise description of what you expected to happen.
39+
40+
**Screenshots**
41+
If applicable, add screenshots to help explain your problem.
42+
43+
**Additional context**
44+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,27 @@
1-
---
2-
name: Feature request
3-
about: Suggest an idea for enhancements to the Accelerator
4-
title: "[FEATURE] Meaningful enhancement description"
5-
labels: enhancement
6-
assignees: Brian969
7-
8-
---
9-
10-
**Required Basic Info**
11-
To properly assess the enhancement request, we require information on the version of the Accelerator you based this request upon:
12-
- Accelerator Version: (eg. v1.1.6)
13-
- Install Type: (Clean or Upgrade)
14-
- Install Branch: (ALZ or Standalone)
15-
- Upgrade from version: (N/A or v1.x.y)
16-
17-
**Is your feature request related to a problem? Please describe.**
18-
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
19-
20-
**Describe the solution you'd like**
21-
A clear and concise description of what you want to happen.
22-
23-
**Describe alternatives you've considered**
24-
A clear and concise description of any alternative solutions or features you've considered.
25-
26-
**Additional context**
27-
Add any other context or screenshots about the feature request here.
1+
---
2+
name: Feature request
3+
about: Suggest an idea for enhancements to the Accelerator
4+
title: "[FEATURE] Meaningful enhancement description"
5+
labels: enhancement
6+
assignees: Brian969
7+
8+
---
9+
10+
**Required Basic Info**
11+
To properly assess the enhancement request, we require information on the version of the Accelerator you based this request upon:
12+
- Accelerator Version: (eg. v1.1.6)
13+
- Install Type: (Clean or Upgrade)
14+
- Install Branch: (ALZ or Standalone)
15+
- Upgrade from version: (N/A or v1.x.y)
16+
17+
**Is your feature request related to a problem? Please describe.**
18+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
19+
20+
**Describe the solution you'd like**
21+
A clear and concise description of what you want to happen.
22+
23+
**Describe alternatives you've considered**
24+
A clear and concise description of any alternative solutions or features you've considered.
25+
26+
**Additional context**
27+
Add any other context or screenshots about the feature request here.

‎.github/PULL_REQUEST_TEMPLATE‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +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.
1+
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

0 commit comments

Comments
 (0)