Skip to content

Commit

Permalink
feat: Add OSS templates
Browse files Browse the repository at this point in the history
  • Loading branch information
Atanda1 committed Jan 9, 2025
1 parent b8ac2d7 commit c52065e
Show file tree
Hide file tree
Showing 4 changed files with 109 additions and 0 deletions.
34 changes: 34 additions & 0 deletions .github/ISSUE_TEMPLATE/Bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''

---

**User Story**
> Add the details of this issue from the user's POV
**Acceptance Criteria(s)**
> 1. **GIVEN** Given that something happens
> **WHEN** Under certain conditions
> **THEN** Then we expect a particular result
**Tech Details**
>Technical changes that will happen include UI changes, styling updates, integration requirements
* **UI State Changes:**
> Changes to the frontend interface
* **Styling Updates:**
> CSS changes for the application
* **Integration Requirements:**
> Changes to the logic parts of the application or protocol

**Design Link**
>* Link to the figma design file
**Notes/Assumptions**
>* Notes or assumption that has to remain constant.
**Open Questions**
33 changes: 33 additions & 0 deletions .github/ISSUE_TEMPLATE/Feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
name: Feature request
about: New feature for this project
title: ''
labels: ''
assignees: ''
---

**User Story**
> Add the details of this issue from the user's POV
**Acceptance Criteria(s)**
> 1. **GIVEN** Given that something happens
> **WHEN** Under certain conditions
> **THEN** Then we expect a particular result
**Tech Details**
>Technical changes that will happen include UI changes, styling updates, integration requirements
* **UI State Changes:**
> Changes to the frontend interface
* **Styling Updates:**
> CSS changes for the application
* **Integration Requirements:**
> Changes to the logic parts of the application or protocol

**Design Link**
>* Link to the figma design file
**Notes/Assumptions**
>* Notes or assumption that has to remain constant.
**Open Questions**
5 changes: 5 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
blank_issues_enabled: false
contact_links:
- name: "General Support"
url: "https://paycrest.io/"
about: "For general inquiries, visit our support page."
37 changes: 37 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
By submitting a PR to this repository, you agree to the terms within the [Paycrest Code of Conduct](https://www.notion.so/paycrest/Contributor-Code-of-Conduct-1602482d45a2806bab75fd314b381f4c?pvs=4). Please see the [contributing guidelines](https://paycrest.notion.site/Contribution-Guide-1602482d45a2809a8930e6ad565c906a?pvs=4) for how to create and submit a high-quality PR for this repo.

### Description

> Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.
>
> Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, contracts etc.
>
> If the UI is being changed, please provide screenshots.

### References

> Include any links supporting this change such as a:
>
> - GitHub Issue/PR number addressed or fixed
> - StackOverflow post
> - Support forum thread
> - Related pull requests/issues from other repos
>
> If there are no references, simply delete this section.
### Testing

> Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this project has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
>
> Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.
>
> Also include details of the environment this PR was developed in (language/platform/browser version).
- [ ] This change adds test coverage for new/changed/fixed functionality

### Checklist

- [ ] I have added documentation for new/changed functionality in this PR
- [ ] All active GitHub checks for tests, formatting, and security are passing
- [ ] The correct base branch is being used, if not `master`

0 comments on commit c52065e

Please sign in to comment.