Skip to content

Commit 313b199

Browse files
SarveshpcSarveshpc
authored
Add files via upload
1 parent c3a4372 commit 313b199

File tree

5 files changed

+232
-0
lines changed

5 files changed

+232
-0
lines changed

‎bug_report.yml‎

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
name: Bug report
2+
description: Submit a bug report to help us improve
3+
title: "[BUG] "
4+
labels: ["C-bug", "S-awaiting-triage"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
We value your time and effort in submitting this bug report. Here are a few things to check before clicking the submit button :)
10+
1. Make sure you're on the latest version of the app. The current release can be found here: https://github.com/juspay/hyperswitch/releases/latest.
11+
2. Search through **both** open and closed issues for your bug: https://github.com/juspay/hyperswitch/issues?q=is%3Aissue+sort%3Aupdated-desc+.
12+
3. Please try to fill this template completely to the best of your abilities. A bug report that is clear and has a reproducible example lets us get to work faster.
13+
14+
- type: textarea
15+
id: bug-description
16+
attributes:
17+
label: Bug Description
18+
description: A clear and concise description of what the bug is.
19+
placeholder: It bugs out when ...
20+
validations:
21+
required: true
22+
23+
- type: textarea
24+
id: expected-behavior
25+
attributes:
26+
label: Expected Behavior
27+
description: What did you think should happen? Add request-response bodies, if applicable.
28+
placeholder: It should ...
29+
validations:
30+
required: true
31+
32+
- type: textarea
33+
id: actual-behavior
34+
attributes:
35+
label: Actual Behavior
36+
description: What did actually happen? Add request-response bodies or screenshots, if applicable.
37+
placeholder: It actually ...
38+
validations:
39+
required: true
40+
41+
- type: textarea
42+
id: steps-to-reproduce
43+
attributes:
44+
label: Steps To Reproduce
45+
description: How do you trigger this bug? Please walk us through it step by step.
46+
value: |
47+
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
48+
1. Go to '...'
49+
2. Click on '....'
50+
3. Scroll down to '....'
51+
validations:
52+
required: true
53+
54+
- type: textarea
55+
id: context
56+
attributes:
57+
label: Context For The Bug
58+
description: How has this issue affected you? What are you trying to accomplish?
59+
placeholder: Providing context (e.g. request-response bodies, stack trace or log data) helps us come up with a solution that is most useful in the real world.
60+
validations:
61+
required: false
62+
63+
- type: textarea
64+
id: environment
65+
attributes:
66+
label: Environment
67+
description: Provide information about the environment where you are running or trying to build the app.
68+
value: |
69+
Are you using hyperswitch hosted version? Yes/No
70+
If yes, please provide the value of the `x-request-id` response header to help us debug your issue.
71+
72+
If not (or if building/running locally), please provide the following details:
73+
1. Operating System or Linux distribution:
74+
2. Rust version (output of `rustc --version`): ``
75+
3. App version (output of `cargo r --features vergen -- --version`): ``
76+
validations:
77+
required: true
78+
79+
- type: checkboxes
80+
id: no-duplicate-issues
81+
attributes:
82+
label: Have you spent some time checking if this bug has been raised before?
83+
options:
84+
- label: I checked and didn't find a similar issue
85+
required: true
86+
87+
- type: checkboxes
88+
id: read-contributing-guidelines
89+
attributes:
90+
label: Have you read the Contributing Guidelines?
91+
options:
92+
- label: I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
93+
required: true
94+
95+
- type: dropdown
96+
id: willing-to-submit-pr
97+
attributes:
98+
label: Are you willing to submit a PR?
99+
description: This is absolutely not required, but we are happy to guide you in the contribution process.
100+
options:
101+
- Yes, I am willing to submit a PR!
102+
- No, but I'm happy to collaborate on a PR with someone else
103+
- No, I don't have time to work on this right now

‎config.toml‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
[target.'cfg(all())']
2+
rustflags = [
3+
"-Funsafe_code",
4+
"-Aclippy::option_map_unit_fn",
5+
"-Wclippy::as_conversions",
6+
"-Wclippy::expect_used",
7+
"-Wclippy::index_refutable_slice",
8+
"-Wclippy::indexing_slicing",
9+
"-Wclippy::match_on_vec_items",
10+
"-Wclippy::missing_panics_doc",
11+
"-Wclippy::out_of_bounds_indexing",
12+
"-Wclippy::panic",
13+
"-Wclippy::panic_in_result_fn",
14+
"-Wclippy::panicking_unwrap",
15+
"-Wclippy::todo",
16+
"-Wclippy::unimplemented",
17+
"-Wclippy::unreachable",
18+
"-Wclippy::unwrap_in_result",
19+
"-Wclippy::unwrap_used",
20+
"-Wclippy::use_self",
21+
# "-Wmissing_debug_implementations",
22+
# "-Wmissing_docs",
23+
"-Wrust_2018_idioms",
24+
"-Wunused_qualifications",
25+
]
26+
27+
[alias]
28+
gen-pg = "generate --path ../../../../connector-template -n"

‎config.yml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
blank_issues_enabled: true
2+
contact_links:
3+
- name: Discord server
4+
url: https://discord.gg/wJZ7DVW8mm
5+
about: Please ask any questions you may have here.
6+
- name: Slack workspace
7+
url: https://join.slack.com/t/hyperswitch-io/shared_invite/zt-2awm23agh-p_G5xNpziv6yAiedTkkqLg
8+
about: Please ask any questions you may have here.
9+
- name: GitHub Discussions
10+
url: https://github.com/juspay/hyperswitch/discussions
11+
about: Please ask and answer questions here.

‎devcontainer.json‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
// For format details, see https://aka.ms/devcontainer.json. For config options, see the
2+
// README at: https://github.com/devcontainers/templates/tree/main/src/docker-existing-dockerfile
3+
{
4+
"name": "Existing Dockerfile",
5+
"build": {
6+
// Sets the run context to one level up instead of the .devcontainer folder.
7+
"context": "..",
8+
// Update the 'dockerFile' property if you aren't using the standard 'Dockerfile' filename.
9+
"dockerfile": "../Dockerfile"
10+
},
11+
"features": {
12+
"ghcr.io/devcontainers-contrib/features/redis-homebrew:1": {}
13+
},
14+
"customizations": {
15+
"vscode": {
16+
"extensions": ["tamasfe.even-better-toml", "rust-lang.rust-analyzer"]
17+
}
18+
},
19+
20+
// Features to add to the dev container. More info: https://containers.dev/features.
21+
// "features": {},
22+
23+
// Use 'forwardPorts' to make a list of ports inside the container available locally.
24+
"forwardPorts": [8080]
25+
26+
// Uncomment the next line to run commands after the container is created.
27+
// "postCreateCommand": "cat /etc/os-release",
28+
29+
// Configure tool-specific properties.
30+
// "customizations": {},
31+
32+
// Uncomment to connect as an existing user other than the container default. More info: https://aka.ms/dev-containers-non-root.
33+
// "remoteUser": "devcontainer"
34+
}

‎feature_request.yml‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
name: Feature request
2+
description: Submit a proposal for a new feature
3+
title: "[FEATURE] "
4+
labels: ["C-feature", "S-awaiting-triage"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
We value your time and efforts in submitting this feature request form. Here are a few things to check before clicking the submit button :)
10+
1. Make sure you're on the latest version of the app. Features are being added all the time, and it is entirely possible what you're requesting has already been added. The current release can be found here: https://github.com/juspay/hyperswitch/releases/latest.
11+
2. Check the changelog file to confirm that the feature hasn't been added for an upcoming release: https://github.com/juspay/hyperswitch/blob/main/CHANGELOG.md
12+
3. Please try to fill this template completely to the best of your abilities. A feature request that is clear and explicit in its needs lets us get to work faster.
13+
14+
- type: textarea
15+
id: feature-description
16+
attributes:
17+
label: Feature Description
18+
description: A clear and concise description of what the feature is.
19+
placeholder: In my use-case, ...
20+
validations:
21+
required: true
22+
23+
- type: textarea
24+
id: implementation
25+
attributes:
26+
label: Possible Implementation
27+
description: A clear and concise description of what you want to happen.
28+
placeholder: Not obligatory, but ideas as to the implementation of the addition or change
29+
validations:
30+
required: true
31+
32+
- type: checkboxes
33+
id: no-duplicate-issues
34+
attributes:
35+
label: Have you spent some time checking if this feature request has been raised before?
36+
options:
37+
- label: I checked and didn't find a similar issue
38+
required: true
39+
40+
- type: checkboxes
41+
id: read-contributing-guidelines
42+
attributes:
43+
label: Have you read the Contributing Guidelines?
44+
options:
45+
- label: I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
46+
required: true
47+
48+
- type: dropdown
49+
id: willing-to-submit-pr
50+
attributes:
51+
label: Are you willing to submit a PR?
52+
description: This is absolutely not required, but we are happy to guide you in the contribution process.
53+
options:
54+
- Yes, I am willing to submit a PR!
55+
- No, but I'm happy to collaborate on a PR with someone else
56+
- No, I don't have time to work on this right now

0 commit comments

Comments
 (0)