Skip to content

Commit 0077d10

Browse files
Cleanup for GitHub Package CI
1 parent 8b6252a commit 0077d10

30 files changed

+3029
-6275
lines changed

.eslintrc.js

+33-40
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,36 @@
11
module.exports = {
2-
root: true,
3-
parserOptions: {
4-
parser: 'babel-eslint',
5-
ecmaVersion: 8
6-
},
7-
env: {
8-
es6: true,
9-
node: true,
10-
browser: true,
11-
jest: true
12-
},
13-
plugins: [
14-
'prettier'
2+
root: true,
3+
parserOptions: {
4+
parser: 'babel-eslint',
5+
ecmaVersion: 8,
6+
},
7+
env: {
8+
es6: true,
9+
node: true,
10+
browser: true,
11+
jest: true,
12+
},
13+
plugins: ['prettier'],
14+
extends: ['eslint:recommended', 'plugin:import/errors', 'plugin:import/warnings', 'prettier'],
15+
rules: {
16+
'prettier/prettier': [
17+
'error',
18+
{
19+
singleQuote: true,
20+
bracketSpacing: true,
21+
semi: false,
22+
printWidth: 500,
23+
},
1524
],
16-
extends: [
17-
'eslint:recommended',
18-
'plugin:import/errors',
19-
'plugin:import/warnings',
20-
'prettier/standard'
25+
'no-empty': [
26+
'error',
27+
{
28+
allowEmptyCatch: true,
29+
},
2130
],
22-
rules: {
23-
'prettier/prettier': [
24-
'error',
25-
{
26-
'singleQuote': true,
27-
'bracketSpacing': true,
28-
'semi': false,
29-
'printWidth': 500
30-
}
31-
],
32-
'no-empty': [
33-
'error',
34-
{
35-
'allowEmptyCatch': true
36-
}
37-
],
38-
'no-console': 0,
39-
'no-control-regex': 0,
40-
'no-useless-escape': 0,
41-
},
42-
globals: {}
43-
}
31+
'no-console': 0,
32+
'no-control-regex': 0,
33+
'no-useless-escape': 0,
34+
},
35+
globals: {},
36+
}

.github/CONTRIBUTING.md

+5-13
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,26 @@
1-
![Logo](https://sfccdevops.s3.amazonaws.com/logo-128.png "Logo")
2-
31
Contributing Guide
42
===
53

6-
<img src="https://octodex.github.com/images/inspectocat.jpg" width="320" style="display: block; margin: 0 auto;">
7-
8-
> We are excited that you are interested in contributing to our project. Before submitting your contribution though, please make sure to take a moment and read through the following guidelines.
9-
104
Issues & Feature Requests
115
---
126

13-
### Bug Fix
7+
[![Create Issue](https://img.shields.io/badge/Github-Create_Issue-red.svg?style=for-the-badge&logo=github&logoColor=ffffff&logoWidth=16)](https://github.com/sfccdevops/sfcc-cartridge-diff/issues/new/choose)
148

15-
[![Staging Environment](https://img.shields.io/badge/Create-Bug_Report-fbca04.svg?style=for-the-badge&logo=github&logoColor=ffffff&logoWidth=16)](https://github.com/sfccdevops/sfcc-cartridge-diff/issues/new?labels=Bug%20Report)
9+
### Bug Fix
1610

1711
> We're sorry things are not working as expected, and want to get things fixed ASAP. In order to help us do that, we need a few things from you.
1812
19-
1. Create a [New Bug Report](https://github.com/sfccdevops/sfcc-cartridge-diff/issues/new?labels=Bug%20Report)
13+
1. Create a [New Issue](https://github.com/sfccdevops/sfcc-cartridge-diff/issues/new/choose)
2014
2. Enter a Short but Descriptive Title for the Issue
2115
3. Use the Template Provided and fill in as much as you can, if something does not apply, enter `N/A`
2216
4. Look for the `Labels` section, and select `Bug Report` from the drop down menu
2317
5. Click `Submit new issue` button
2418

2519
### Feature Request
2620

27-
[![Staging Environment](https://img.shields.io/badge/Create-Feature_Request-9933cc.svg?style=for-the-badge&logo=github&logoColor=ffffff&logoWidth=16)](https://github.com/sfccdevops/sfcc-cartridge-diff/issues/new?labels=Feature%20Request)
28-
2921
> Got an idea for a new feature? We'd love to hear it! In order to get this knocked out, we will need a few things from you.
3022
31-
1. Create a [New Feature Request](https://github.com/sfccdevops/sfcc-cartridge-diff/issues/new?labels=Feature%20Request)
23+
1. Create a [New Issue](https://github.com/sfccdevops/sfcc-cartridge-diff/issues/new/choose)
3224
2. Enter a Short but Descriptive Title for the Feature Request
3325
3. Use the Template Provided and fill in as much as you can, if something does not apply, enter `N/A` ( you can delete the `Steps to Duplicate:` section as that does not apply )
3426
4. Look for the `Labels` section, and select `Feature Request` from the drop down menu
@@ -37,7 +29,7 @@ Issues & Feature Requests
3729
Pull Requests
3830
---
3931

40-
[![Staging Environment](https://img.shields.io/badge/Create-Pull_Request-006b75.svg?style=for-the-badge&logo=github&logoColor=ffffff&logoWidth=16)](https://github.com/sfccdevops/sfcc-cartridge-diff/compare?labels=Ready%20For%20Code%20Review)
32+
[![Create Pull Request](https://img.shields.io/badge/Github-Create_Pull_Request-blue.svg?style=for-the-badge&logo=github&logoColor=ffffff&logoWidth=16)](https://github.com/sfccdevops/sfcc-cartridge-diff/compare)
4133

4234
### Bug Fix
4335

.github/ISSUE_TEMPLATE/bug-report.yml

+66
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
name: Bug Report
2+
description: I would like to Report a Bug
3+
labels: [Bug Report]
4+
assignees:
5+
- manifestinteractive
6+
body:
7+
- type: checkboxes
8+
attributes:
9+
label: Is there an existing issue for this?
10+
description: Please search to see if an issue already exists for the bug you encountered.
11+
options:
12+
- label: I have searched the existing issues
13+
required: true
14+
- type: textarea
15+
attributes:
16+
label: Describe the Bug
17+
description: A clear and concise description of what the bug is.
18+
validations:
19+
required: true
20+
- type: textarea
21+
attributes:
22+
label: Steps To Reproduce
23+
description: Steps to reproduce the behavior.
24+
placeholder: |
25+
1. Go to ...
26+
2. Click on ...
27+
3. Scroll down to ...
28+
4. See error ...
29+
validations:
30+
required: true
31+
- type: textarea
32+
attributes:
33+
label: Expected Behavior
34+
description: A concise description of what you expected to happen.
35+
validations:
36+
required: false
37+
- type: textarea
38+
attributes:
39+
label: Screenshots
40+
description: If applicable, add screenshots to help explain your problem.
41+
validations:
42+
required: false
43+
- type: textarea
44+
attributes:
45+
label: Environment
46+
description: |
47+
examples:
48+
- **OS**: Ubuntu 20.04
49+
- **Node**: 13.14.0
50+
- **npm**: 7.6.3
51+
value: |
52+
- OS:
53+
- Node:
54+
- npm:
55+
render: markdown
56+
validations:
57+
required: false
58+
- type: textarea
59+
attributes:
60+
label: Additional Context
61+
description: |
62+
Links? References? Anything that will give us more context about the issue you are encountering!
63+
64+
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
65+
validations:
66+
required: false

.github/ISSUE_TEMPLATE/bug_report.md

-32
This file was deleted.

.github/ISSUE_TEMPLATE/custom.md

-8
This file was deleted.
+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
name: Feature Request
2+
description: This is a new Feature Request for this project
3+
labels: [Feature Request]
4+
assignees:
5+
- manifestinteractive
6+
body:
7+
- type: textarea
8+
attributes:
9+
label: Describe the Problem
10+
description: Is your feature request related to a problem? Please describe.
11+
placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
validations:
13+
required: true
14+
- type: textarea
15+
attributes:
16+
label: Describe the Solution
17+
description: Describe the solution you'd like
18+
placeholder: A clear and concise description of what you want to happen.
19+
validations:
20+
required: true
21+
- type: textarea
22+
attributes:
23+
label: Alternatives
24+
description: Describe alternatives you've considered
25+
placeholder: A clear and concise description of any alternative solutions or features you've considered.
26+
validations:
27+
required: false
28+
- type: textarea
29+
attributes:
30+
label: Additional Context
31+
description: |
32+
Add any other context or screenshots about the feature request here.
33+
34+
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
35+
validations:
36+
required: false

.github/ISSUE_TEMPLATE/feature_request.md

-20
This file was deleted.

.github/ISSUE_TEMPLATE/question.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
name: Question
2+
description: I have a Question about this project
3+
labels: [Question]
4+
assignees:
5+
- manifestinteractive
6+
body:
7+
- type: textarea
8+
attributes:
9+
label: Question
10+
description: Please Write your Question Below.
11+
validations:
12+
required: true
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
name: Requested Change
2+
description: This is a Requested Change to the project
3+
labels: [Requested Change]
4+
assignees:
5+
- manifestinteractive
6+
body:
7+
- type: textarea
8+
attributes:
9+
label: Describe the Problem
10+
description: Is your requested change related to a problem? Please describe.
11+
placeholder: A clear and concise description of what the request is.
12+
validations:
13+
required: true
14+
- type: textarea
15+
attributes:
16+
label: Describe the Solution
17+
description: Describe the solution you'd like
18+
placeholder: A clear and concise description of what you want to happen.
19+
validations:
20+
required: true
21+
- type: textarea
22+
attributes:
23+
label: Alternatives
24+
description: Describe alternatives you've considered
25+
placeholder: A clear and concise description of any alternative solutions or features you've considered.
26+
validations:
27+
required: false
28+
- type: textarea
29+
attributes:
30+
label: Additional Context
31+
description: |
32+
Add any other context or screenshots about the feature request here.
33+
34+
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
35+
validations:
36+
required: false

.github/PULL_REQUEST_TEMPLATE.md

+4-6
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,25 @@
1-
Overview:
1+
Overview
22
---
33

44
TEXT
55

6-
Reviewer:
6+
Reviewer
77
---
88

99
> Where should the reviewer start? How to Test? Background Context? etc ( required )
1010
1111
TEXT
1212

13-
Checklist:
13+
Checklist
1414
---
1515

1616
> I have tested each of the following, and they work as expected: ( required )
1717
1818
- [ ] Meets [Contributing Guide](https://github.com/sfccdevops/sfcc-cartridge-diff/blob/develop/.github/CONTRIBUTING.md) Requirements
1919
- [ ] Pulled in the Latest Code from the `develop` branch
2020
- [ ] Works on a Desktop / Laptop Device
21-
- [ ] Works on a Mobile Device
22-
- [ ] `npm test` Does Not Generate Errors
2321

24-
Documentation:
22+
Documentation
2523
---
2624

2725
> Screenshots, Attachments, Linked GitHub Issues, etc ( optional )

.github/workflows/assign_to_project.yml

-20
This file was deleted.

0 commit comments

Comments
 (0)