Skip to content

Commit 61bba2b

Browse files
committed
deloy
1 parent d213586 commit 61bba2b

39 files changed

+2491
-231
lines changed

.dependabot/config.yml

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
version: 1
2+
update_configs:
3+
- package_manager: "ruby:bundler"
4+
directory: "/"
5+
update_schedule: "live"
6+
automerged_updates:
7+
- match:
8+
dependency_name: "spree*"
9+
update_type: "semver:patch"
10+
- match:
11+
dependency_name: "rails"
12+
update_type: "semver:patch"
13+
- match:
14+
dependency_name: "rubocop*"
15+
- match:
16+
dependency_name: "puma"
17+
- match:
18+
dependency_name: "rack*"
19+
- match:
20+
dependency_name: "sentry-raven"
21+
- match:
22+
dependency_name: "scout_apm"
23+
- match:
24+
dependency_name: "flipper*"
25+
update_type: "semver:minor"
26+
- match:
27+
dependency_name: "sidekiq"
28+
update_type: "semver:minor"
29+
- match:
30+
dependency_name: "aws-sdk-s3"
31+
update_type: "semver:minor"
32+
- match:
33+
dependency_name: "mini_racer"
34+
- match:
35+
dependency_name: "sass-rails"
36+
- match:
37+
dependency_name: "awesome_print"
38+
- match:
39+
dependency_name: "pry*"
40+
- match:
41+
dependency_name: "rspec*"
42+
- match:
43+
dependency_name: "webdrivers"
44+
- match:
45+
dependency_name: "sendgrid-actionmailer"

.github/CODEOWNERS

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
.github/workflows/* @saleor/sre

.github/CODE_OF_CONDUCT.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28+
29+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30+
31+
## Scope
32+
33+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello+community@saleor.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38+
39+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44+
45+
[homepage]: http://contributor-covenant.org
46+
[version]: http://contributor-covenant.org/version/1/4/
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
name: Bug report
2+
description: Create a bug report
3+
title: "Bug: "
4+
labels: ["bug", "triage"]
5+
6+
body:
7+
- type: textarea
8+
id: goal
9+
attributes:
10+
label: What are you trying to achieve?
11+
description: Describe your goal, use case, or provide context of your problem from the business point of view.
12+
validations:
13+
required: true
14+
- type: textarea
15+
id: steps
16+
attributes:
17+
label: Steps to reproduce the problem
18+
description: Reproduction steps starting with an empty database. You can use a free Saleor Cloud environment as a quick starting point.
19+
placeholder: |
20+
1. Create a product with two attributes…
21+
2. …
22+
3. Run `…`
23+
4. See that it failed with…
24+
validations:
25+
required: true
26+
- type: textarea
27+
id: expected-behavior
28+
attributes:
29+
label: What did you expect to happen?
30+
description: Describe why the behavior described earlier is incorrect.
31+
validations:
32+
required: true
33+
- type: textarea
34+
id: logs
35+
attributes:
36+
label: Logs
37+
description: Include any logs from the console, screenshots, and any API queries or responses that could help us understand the problem. Make sure to omit any personal identifiable information or data sensitive to your business.
38+
validations:
39+
required: false
40+
- type: textarea
41+
id: environment
42+
attributes:
43+
label: Environment
44+
description: Provide some information about your environment.
45+
value: |
46+
Saleor version: …
47+
OS and version: …
48+
validations:
49+
required: true

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: 💬 GitHub Discussions
4+
url: https://github.com/saleor/saleor/discussions
5+
about: If you have a support question or need help getting Saleor to work, please use GitHub Discussions.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: Feature request
6+
assignees: ''
7+
8+
---
9+
10+
### What I'm trying to achieve
11+
12+
13+
### Describe a proposed solution
14+
...
15+
16+
### Other solutions I've tried and won't work
17+
18+
19+
### Screenshots or mockups
20+
<!-- Please provide any illustrations that could help others understand the problem or the proposed solution. -->

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
I want to merge this change because...
2+
3+
<!-- Please mention all relevant issue numbers. -->
4+
5+
# Impact
6+
7+
* [ ] New migrations
8+
* [ ] New/Updated API fields or mutations
9+
* [ ] Deprecated API fields or mutations
10+
* [ ] Removed API types, fields, or mutations
11+
* [ ] Documentation needs to be updated
12+
13+
# Pull Request Checklist
14+
15+
<!-- Please keep this section. It will make the maintainer's life easier. -->
16+
17+
* [ ] Privileged queries and mutations are guarded by proper permission checks
18+
* [ ] Database queries are optimized and the number of queries is constant
19+
* [ ] Database migration files are up to date
20+
* [ ] The changes are tested
21+
* [ ] GraphQL schema and type definitions are up to date
22+
* [ ] Changes are mentioned in the changelog

.github/badges/twitter.svg

Lines changed: 1 addition & 0 deletions
Loading

.github/dependabot.yml

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: pip
4+
directory: "/"
5+
schedule:
6+
interval: weekly
7+
time: "04:00"
8+
open-pull-requests-limit: 10
9+
ignore:
10+
- dependency-name: django-graphql-jwt
11+
versions:
12+
- "> 0.3.0"
13+
- dependency-name: black
14+
versions:
15+
- 21.4b0
16+
- dependency-name: adyen
17+
versions:
18+
- 5.0.0
19+
- 5.1.0
20+
- dependency-name: faker
21+
versions:
22+
- 7.0.1
23+
- dependency-name: django-countries
24+
versions:
25+
- "7.1"
26+
- dependency-name: mypy
27+
versions:
28+
- "0.812"
29+
- dependency-name: pytest-xdist
30+
versions:
31+
- 2.2.1

.github/graphql-inspector.yaml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
branch: "main"
2+
schema: "saleor/graphql/schema.graphql"
3+
diff:
4+
# Pull Request annotations
5+
annotations: true
6+
# Merge Pull Request's branch with the target branch to get the schema
7+
experimental_merge: true
8+
# Label to mark Pull Request introducing breaking changes as safe and expected
9+
approveLabel: 'approved-breaking-change'
10+
# Limit a list of changes in summary
11+
summaryLimit: 200

0 commit comments

Comments
 (0)