mirror of
https://github.com/marcogll/passkit-generator.git
synced 2026-03-15 18:25:24 +00:00
Merge branch 'feature/github-templates'
This commit is contained in:
72
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
72
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
@@ -0,0 +1,72 @@
|
|||||||
|
---
|
||||||
|
name: Bug report
|
||||||
|
about: If you suspect to have found a bug in passkit-generator, open a bug report. Thanks for helping passkit-generator improve!
|
||||||
|
title: ""
|
||||||
|
labels: ["Needs Triage"]
|
||||||
|
assignees: ""
|
||||||
|
---
|
||||||
|
|
||||||
|
## Running OS
|
||||||
|
|
||||||
|
<!-- Include the version -->
|
||||||
|
|
||||||
|
## Running Node Version
|
||||||
|
|
||||||
|
<!--
|
||||||
|
Add Node version. It is obvious, but all the sections have a comment.
|
||||||
|
Having this without a comment would have sucked. So, here it is 😄
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Description
|
||||||
|
|
||||||
|
<!-- Provide as much information you can about the possible bug. Who reads is not in your head! :) -->
|
||||||
|
|
||||||
|
## Expected behavior
|
||||||
|
|
||||||
|
<!--
|
||||||
|
What do you expect to happen?
|
||||||
|
Is it something documented in API document or
|
||||||
|
in any other document in wiki or README, which
|
||||||
|
is not honored?
|
||||||
|
|
||||||
|
If so, also report the piece where contraddiction happens,
|
||||||
|
like below:
|
||||||
|
|
||||||
|
> Use markdown quote
|
||||||
|
> section to report
|
||||||
|
> the contraddiction
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Steps to reproduce
|
||||||
|
|
||||||
|
<!--
|
||||||
|
Create a list of steps, if any, or report a code useful for reproducing the issue.
|
||||||
|
You can also link a repo with the repro-case.
|
||||||
|
-->
|
||||||
|
|
||||||
|
<!--
|
||||||
|
If you need to share private details, like certificates
|
||||||
|
or an output of your pass that you don't want to show
|
||||||
|
publicly, you can send it to me on Telegram: https://t.me/AlexandrCerutti.
|
||||||
|
The main conversation will still happen here on Github.
|
||||||
|
|
||||||
|
You are kindly requested to report the issue number when writing the message.
|
||||||
|
You are also kindly requested to write in English.
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Were you able to verify it by using (and changing) the examples?
|
||||||
|
|
||||||
|
<!-- Yes / No -->
|
||||||
|
<!-- If no, it might be a problem with the application of yours -->
|
||||||
|
|
||||||
|
## If yes, which changes did you apply?
|
||||||
|
|
||||||
|
<!-- Report the changes. Reporting using a fork of passkit-generator is appreciated -->
|
||||||
|
|
||||||
|
## Other details
|
||||||
|
|
||||||
|
- [ ] I'm available to open a Pull Request to resolve the problem (after the triage)
|
||||||
|
|
||||||
|
<!-- Write here below whatever comes through your mind about the bug and passkit-generator -->
|
||||||
|
|
||||||
|
<!-- Do you like the project? Did you already left a ⭐️ on the project? I'll be happy to help, but happier if you already left a start 😄 (literally, my dopamine arises) -->
|
||||||
9
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
9
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
@@ -0,0 +1,9 @@
|
|||||||
|
blank_issues_enabled: true
|
||||||
|
contact_links:
|
||||||
|
- name: Feature Request
|
||||||
|
about: Propose a new feature in discussions. Click the link to open one with a template
|
||||||
|
url: https://github.com/alexandercerutti/passkit-generator/discussions/new?category=ideas&title=[Feature%20Request]%20<!--%20Write%20Subject%20-->
|
||||||
|
|
||||||
|
- name: Security Issues
|
||||||
|
about: Contact me privately on Telegram for security issues
|
||||||
|
url: https://t.me/AlexandrCerutti
|
||||||
31
.github/pull_request_template.md
vendored
Normal file
31
.github/pull_request_template.md
vendored
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
<!--
|
||||||
|
Thank you for your contribution to passkit-generator.
|
||||||
|
You'll be responded to as soon as possible. (but I
|
||||||
|
assure you will be responded! 😉)
|
||||||
|
|
||||||
|
Meanwhile, what about leaving a ⭐️ on the project? That
|
||||||
|
would be very helpful for making it even more known. 🔝
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Description
|
||||||
|
|
||||||
|
<!--
|
||||||
|
Write here below a description about what you are trying to change.
|
||||||
|
Also include, if needed, any information about the platform you tested on.
|
||||||
|
|
||||||
|
If this pull request attempts to close an already opened issue, use issue
|
||||||
|
linkers identifiers like "Fixes #99", to link it automatically. See the
|
||||||
|
identifiers at the following page:
|
||||||
|
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Check relevant checkboxes
|
||||||
|
|
||||||
|
- [ ] I've run tests (through `npm test`) and they passed
|
||||||
|
- [ ] I generated a working Apple Wallet Pass after the change
|
||||||
|
- [ ] Provided examples keep working after the change
|
||||||
|
- [ ] This improvement is or might be a breaking change
|
||||||
|
|
||||||
|
## Relevant information
|
||||||
|
|
||||||
|
<!-- Add any other relevant details to the PR (test, technical details, ...) -->
|
||||||
Reference in New Issue
Block a user