-
Notifications
You must be signed in to change notification settings - Fork 41
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
7 changed files
with
189 additions
and
189 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,68 +1,68 @@ | ||
| name: Bug report | ||
| description: Create a report to help Quinoa improve | ||
| title: 'Issue Title' | ||
| labels: ['Status: needs triage'] | ||
| body: | ||
| - type: textarea | ||
| id: description | ||
| attributes: | ||
| label: Describe the bug | ||
| description: A clear and concise description of what the bug is. | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: quinoa-version | ||
| attributes: | ||
| label: Quinoa version | ||
| placeholder: x.x.x | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: quarkus-version | ||
| attributes: | ||
| label: Quarkus version | ||
| placeholder: x.x.x | ||
| validations: | ||
| required: true | ||
| - type: dropdown | ||
| id: engine | ||
| attributes: | ||
| label: Build / Runtime | ||
| multiple: false | ||
| options: | ||
| - Vite | ||
| - Angular | ||
| - Create React App (CRA) | ||
| - Next.js | ||
| - Other | ||
| validations: | ||
| required: true | ||
| - type: dropdown | ||
| id: package-manager | ||
| attributes: | ||
| label: Package Manager | ||
| multiple: false | ||
| options: | ||
| - NPM | ||
| - PNPM | ||
| - YARN | ||
| - OTHER | ||
| - type: textarea | ||
| id: reproduce-steps | ||
| attributes: | ||
| label: Steps to reproduce the behavior | ||
| description: A clear and concise description of how to make the issue happen. | ||
| placeholder: > | ||
| 1. Go to '...' | ||
| 2. Click on '....' | ||
| 3. Scroll down to '....' | ||
| 4. See error | ||
| validations: | ||
| required: false | ||
| - type: textarea | ||
| id: expected-behavior | ||
| attributes: | ||
| label: Expected behavior | ||
| description: A clear and concise description of what you expected to happen. | ||
| validations: | ||
| required: false | ||
| name: Bug report | ||
| description: Create a report to help Quinoa improve | ||
| title: 'Issue Title' | ||
| labels: ['Status: needs triage'] | ||
| body: | ||
| - type: textarea | ||
| id: description | ||
| attributes: | ||
| label: Describe the bug | ||
| description: A clear and concise description of what the bug is. | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: quinoa-version | ||
| attributes: | ||
| label: Quinoa version | ||
| placeholder: x.x.x | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: quarkus-version | ||
| attributes: | ||
| label: Quarkus version | ||
| placeholder: x.x.x | ||
| validations: | ||
| required: true | ||
| - type: dropdown | ||
| id: engine | ||
| attributes: | ||
| label: Build / Runtime | ||
| multiple: false | ||
| options: | ||
| - Vite | ||
| - Angular | ||
| - Create React App (CRA) | ||
| - Next.js | ||
| - Other | ||
| validations: | ||
| required: true | ||
| - type: dropdown | ||
| id: package-manager | ||
| attributes: | ||
| label: Package Manager | ||
| multiple: false | ||
| options: | ||
| - NPM | ||
| - PNPM | ||
| - YARN | ||
| - OTHER | ||
| - type: textarea | ||
| id: reproduce-steps | ||
| attributes: | ||
| label: Steps to reproduce the behavior | ||
| description: A clear and concise description of how to make the issue happen. | ||
| placeholder: > | ||
| 1. Go to '...' | ||
| 2. Click on '....' | ||
| 3. Scroll down to '....' | ||
| 4. See error | ||
| validations: | ||
| required: false | ||
| - type: textarea | ||
| id: expected-behavior | ||
| attributes: | ||
| label: Expected behavior | ||
| description: A clear and concise description of what you expected to happen. | ||
| validations: | ||
| required: false |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,15 +1,15 @@ | ||
| --- | ||
| name: Feature request | ||
| about: Suggest an idea for this project | ||
| title: '' | ||
| labels: feature | ||
| assignees: '' | ||
|
|
||
| --- | ||
| <!-- A clear and concise description of what the feature is.--> | ||
| ## Feature idea | ||
|
|
||
| <!--Any additional information you can provide, like an overall design description--> | ||
| ## Additional information | ||
|
|
||
| <!-- Feel free to attach your feature screenshorts.--> | ||
| --- | ||
| name: Feature request | ||
| about: Suggest an idea for this project | ||
| title: '' | ||
| labels: feature | ||
| assignees: '' | ||
|
|
||
| --- | ||
| <!-- A clear and concise description of what the feature is.--> | ||
| ## Feature idea | ||
|
|
||
| <!--Any additional information you can provide, like an overall design description--> | ||
| ## Additional information | ||
|
|
||
| <!-- Feel free to attach your feature screenshorts.--> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,21 @@ | ||
| <!-- Describe your changes below that what did you made change --> | ||
| ## Describe your changes | ||
|
|
||
| <!-- If your PR fixes an open issue then use Closes #31 --> | ||
| ## Fixes Issue | ||
|
|
||
|
|
||
| <!-- Mark all the applicable boxes. To mark the box as done follow the following conventions --> | ||
| <!-- | ||
| [x] - Correct; marked as done | ||
| [X] - Correct; marked as done | ||
| [ ] - Not correct; marked as **not** done --> | ||
|
|
||
| ## Check List (Check all the applicable boxes) <!-- Follow the above conventions to check the box --> | ||
|
|
||
| - [ ] My code follows the code style of this project. | ||
| - [ ] My change requires changes to the documentation. | ||
| - [ ] I have updated the documentation accordingly. | ||
| - [ ] All new and existing tests passed. | ||
| <!-- Describe your changes below that what did you made change --> | ||
| ## Describe your changes | ||
|
|
||
| <!-- If your PR fixes an open issue then use Closes #31 --> | ||
| ## Fixes Issue | ||
|
|
||
|
|
||
| <!-- Mark all the applicable boxes. To mark the box as done follow the following conventions --> | ||
| <!-- | ||
| [x] - Correct; marked as done | ||
| [X] - Correct; marked as done | ||
| [ ] - Not correct; marked as **not** done --> | ||
|
|
||
| ## Check List (Check all the applicable boxes) <!-- Follow the above conventions to check the box --> | ||
|
|
||
| - [ ] My code follows the code style of this project. | ||
| - [ ] My change requires changes to the documentation. | ||
| - [ ] I have updated the documentation accordingly. | ||
| - [ ] All new and existing tests passed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,39 +1,39 @@ | ||
| ## Contributor Covenant Code of Conduct | ||
|
|
||
| ### Our Pledge | ||
| 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, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. | ||
|
|
||
| ### Our Standards | ||
| Examples of behavior that contributes to creating a positive environment include: | ||
|
|
||
| - Using welcoming and inclusive language | ||
| - Being respectful of differing viewpoints and experiences | ||
| - Gracefully accepting constructive criticism | ||
| - Focusing on what is best for the community | ||
| - Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| - The use of sexualized language or imagery and unwelcome sexual attention or advances | ||
| - Trolling, insulting/derogatory comments, and personal or political attacks | ||
| - Public or private harassment | ||
| - Publishing others' private information, such as a physical or electronic address, without explicit permission | ||
| - Other conduct which could reasonably be considered inappropriate in a professional setting | ||
|
|
||
| ### Our Responsibilities | ||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| ### Scope | ||
| 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. | ||
|
|
||
| ### Enforcement | ||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and 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. | ||
|
|
||
| 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. | ||
|
|
||
| ### Attribution | ||
| This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html | ||
|
|
||
| ## Contributor Covenant Code of Conduct | ||
|
|
||
| ### Our Pledge | ||
| 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, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. | ||
|
|
||
| ### Our Standards | ||
| Examples of behavior that contributes to creating a positive environment include: | ||
|
|
||
| - Using welcoming and inclusive language | ||
| - Being respectful of differing viewpoints and experiences | ||
| - Gracefully accepting constructive criticism | ||
| - Focusing on what is best for the community | ||
| - Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| - The use of sexualized language or imagery and unwelcome sexual attention or advances | ||
| - Trolling, insulting/derogatory comments, and personal or political attacks | ||
| - Public or private harassment | ||
| - Publishing others' private information, such as a physical or electronic address, without explicit permission | ||
| - Other conduct which could reasonably be considered inappropriate in a professional setting | ||
|
|
||
| ### Our Responsibilities | ||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| ### Scope | ||
| 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. | ||
|
|
||
| ### Enforcement | ||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and 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. | ||
|
|
||
| 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. | ||
|
|
||
| ### Attribution | ||
| This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html | ||
|
|
||
| For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,48 +1,48 @@ | ||
| ## Contributing at quarkus-quinoa | ||
| We are beyond excited to see that you want to contribute! We would love to accept your contributions. Navigate through the following to understand more about contributing. | ||
|
|
||
| ### Prerequisites | ||
| - Java 11 | ||
| - Apache Maven | ||
|
|
||
| ## Follow the Steps | ||
| - [Fork the repository](https://github.com/quarkiverse/quarkus-quinoa/fork) | ||
|
|
||
| - Clone the project locally | ||
|
|
||
| ``` | ||
| git clone https://github.com/shivam-sharma7/quarkus-quinoa.git | ||
| ``` | ||
| **Note:** In the place of `shivam-sharma7` you have to add your github username. | ||
|
|
||
| - Create a new branch | ||
|
|
||
| ``` | ||
| git checkout -b <your branch_name> | ||
| ``` | ||
|
|
||
| After creating new branch start making your changes and once the changes done then push your changes and then create a ` pull_request` | ||
| - Push your changes | ||
|
|
||
| ``` | ||
| git push origin <your branch_name> | ||
| ``` | ||
|
|
||
| Now you have to wait for the review. The project maintainer will review your PR and once your PR got approve then they will merged it. If you want to support, please give a ⭐ | ||
|
|
||
| ### Things to remember before making changes | ||
|
|
||
| Before making any contribution make sure your local `main` keep up-to-date with upstream `main`. To do that type the following commands. | ||
|
|
||
| - First add upstream | ||
| ``` | ||
| git remote add upstream https://github.com/quarkiverse/quarkus-quinoa.git | ||
| ``` | ||
| - Pull all changes from upstream | ||
| ``` | ||
| git pull upstream main | ||
| ``` | ||
| - Keep your fork up-to-date | ||
| ``` | ||
| git push origin main | ||
| ## Contributing at quarkus-quinoa | ||
| We are beyond excited to see that you want to contribute! We would love to accept your contributions. Navigate through the following to understand more about contributing. | ||
|
|
||
| ### Prerequisites | ||
| - Java 11 | ||
| - Apache Maven | ||
|
|
||
| ## Follow the Steps | ||
| - [Fork the repository](https://github.com/quarkiverse/quarkus-quinoa/fork) | ||
|
|
||
| - Clone the project locally | ||
|
|
||
| ``` | ||
| git clone https://github.com/shivam-sharma7/quarkus-quinoa.git | ||
| ``` | ||
| **Note:** In the place of `shivam-sharma7` you have to add your github username. | ||
|
|
||
| - Create a new branch | ||
|
|
||
| ``` | ||
| git checkout -b <your branch_name> | ||
| ``` | ||
|
|
||
| After creating new branch start making your changes and once the changes done then push your changes and then create a ` pull_request` | ||
| - Push your changes | ||
|
|
||
| ``` | ||
| git push origin <your branch_name> | ||
| ``` | ||
|
|
||
| Now you have to wait for the review. The project maintainer will review your PR and once your PR got approve then they will merged it. If you want to support, please give a ⭐ | ||
|
|
||
| ### Things to remember before making changes | ||
|
|
||
| Before making any contribution make sure your local `main` keep up-to-date with upstream `main`. To do that type the following commands. | ||
|
|
||
| - First add upstream | ||
| ``` | ||
| git remote add upstream https://github.com/quarkiverse/quarkus-quinoa.git | ||
| ``` | ||
| - Pull all changes from upstream | ||
| ``` | ||
| git pull upstream main | ||
| ``` | ||
| - Keep your fork up-to-date | ||
| ``` | ||
| git push origin main | ||
| ``` |
Binary file not shown.
Binary file not shown.