mirror of
https://github.com/LawnchairLauncher/lawnchair.git
synced 2026-02-11 06:44:00 +00:00
Add issue templates and other files (#2749)
This commit is contained in:
SuperDragonXD
1
.github/ISSUE_TEMPLATE/bug_report.yaml
vendored
1
.github/ISSUE_TEMPLATE/bug_report.yaml
vendored
@@ -1,6 +1,7 @@
|
||||
name: Bug report
|
||||
description: Create a report to help us address issues you are facing with the app
|
||||
title: "[BUG] "
|
||||
labels: [bug]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
|
||||
55
.github/ISSUE_TEMPLATE/feature_request.yaml
vendored
Normal file
55
.github/ISSUE_TEMPLATE/feature_request.yaml
vendored
Normal file
@@ -0,0 +1,55 @@
|
||||
name: Feature request
|
||||
description: Suggest features you want the devs (or contributors) to make for the app
|
||||
title: "[FEATURE] "
|
||||
labels: [feature, enhancement]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
Thanks for taking the time to file this issue! Here are a few things to check before clicking the submit button :)
|
||||
1. Make sure you're on the latest version of the app. The current release can be found here: https://github.com/LawnchairLauncher/lawnchair/releases.
|
||||
2. The feature might already be in the [development versions](https://github.com/LawnchairLauncher/lawnchair/wiki/FAQ#development-versions). You can try testing and see if the feature already exists.
|
||||
3. Search through **both** open and closed issues for your feature: https://github.com/LawnchairLauncher/lawnchair/issues?q=is%3Aissue+sort%3Aupdated-desc+.
|
||||
4. ALWAYS fill this template. If you fail to do so, your issue will be immediately closed with no response. Maintaining open source projects for free is hard work, and we expect users to respect that time and effort by putting in a little bit of their own. That helps us implement your feature faster and in return you get a better app — everybody wins.
|
||||
- type: textarea
|
||||
id: feature-description
|
||||
attributes:
|
||||
label: Describe the feature
|
||||
description: A clear and concise description of what the feature is.
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: feature-usefulness
|
||||
attributes:
|
||||
label: Why would it be useful to add?
|
||||
description: Explain why this feature would be useful to you
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: dropdown
|
||||
id: feature-in-version-two
|
||||
attributes:
|
||||
label: Did the feature exist in Lawnchair v2? (Play Store version)
|
||||
description: If so, the feature might be already in the dev's to-do list and may be closed. See [this page](https://github.com/LawnchairLauncher/lawnchair/wiki/FAQ#can-you-return-x-feature-from-lawnchair-2) for more information.
|
||||
options:
|
||||
- "Yes"
|
||||
- "No"
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: feature-examples
|
||||
attributes:
|
||||
label: Example(s)
|
||||
description: Post screenshots/drawings/links/etc of the feature request, or proof-of-concept images about the feature.
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: additional-context
|
||||
attributes:
|
||||
label: Additional context
|
||||
description: Add any other context about the feature here.
|
||||
validations:
|
||||
required: false
|
||||
12
.github/ISSUE_TEMPLATE/general_discussion.yaml
vendored
Normal file
12
.github/ISSUE_TEMPLATE/general_discussion.yaml
vendored
Normal file
@@ -0,0 +1,12 @@
|
||||
name: General Discussion
|
||||
description: Want to discuss something that doesn't fit in the other issue templates? Use this template.
|
||||
title: "[DISCUSSION] "
|
||||
labels: [discussion]
|
||||
body:
|
||||
- type: textarea
|
||||
id: question
|
||||
attributes:
|
||||
label: About this discussion
|
||||
description: Add the contents of your discussion here.
|
||||
validations:
|
||||
required: true
|
||||
21
.github/ISSUE_TEMPLATE/question_support.yaml
vendored
Normal file
21
.github/ISSUE_TEMPLATE/question_support.yaml
vendored
Normal file
@@ -0,0 +1,21 @@
|
||||
name: Question or Support Request
|
||||
description: Ask a question or provide details of your support request here.
|
||||
title: "[QUESTION] "
|
||||
labels: [question]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
Note: We highly recommend posting your question/support request on either [Telegram](https://t.co/qYev4OkvpT) or [Discord](https://discord.com/invite/3x8qNWxgGZ).
|
||||
|
||||
Before posting any question or ask for support, first read the project's README.md file and
|
||||
the WIKI pages or any other additional documentation that might be listed
|
||||
in the project's README.md file.
|
||||
|
||||
- type: textarea
|
||||
id: question
|
||||
attributes:
|
||||
label: Describe your question or ask for support
|
||||
description: A clear and concise description of what your doubt is.
|
||||
validations:
|
||||
required: true
|
||||
13
.github/pull_request_template.md
vendored
Normal file
13
.github/pull_request_template.md
vendored
Normal file
@@ -0,0 +1,13 @@
|
||||
## Description
|
||||
|
||||
<!-- Please include a summary of the change. Please also include relevant motivation and context. -->
|
||||
|
||||
|
||||
Fixes # (issue) <!-- optional -->
|
||||
|
||||
## Type of change
|
||||
|
||||
- [ ] General change (non-breaking change that fixes typos/grammar, or adds additional content that isn't a bug or a feature)
|
||||
- [ ] Bug fix (non-breaking change which fixes an issue)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
19
.github/workflows/close_stale_issues.yml
vendored
Normal file
19
.github/workflows/close_stale_issues.yml
vendored
Normal file
@@ -0,0 +1,19 @@
|
||||
name: 'Close stale issues and PRs'
|
||||
on:
|
||||
schedule:
|
||||
- cron: '30 1 * * *'
|
||||
|
||||
jobs:
|
||||
stale:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/stale@v5
|
||||
with:
|
||||
stale-issue-message: 'This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.'
|
||||
stale-pr-message: 'This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.'
|
||||
close-issue-message: 'This issue was closed because it has been stale for 5 days with no activity.'
|
||||
close-pr-message: 'This PR was closed because it has been stale for 10 days with no activity.'
|
||||
days-before-issue-stale: 30
|
||||
days-before-pr-stale: 30
|
||||
days-before-issue-close: 5
|
||||
days-before-pr-close: 10
|
||||
128
CODE_OF_CONDUCT
Normal file
128
CODE_OF_CONDUCT
Normal file
@@ -0,0 +1,128 @@
|
||||
# Contributor Covenant Code of Conduct
|
||||
|
||||
## Our Pledge
|
||||
|
||||
We as members, contributors, and leaders pledge to make participation in our
|
||||
community a harassment-free experience for everyone, regardless of age, body
|
||||
size, visible or invisible 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.
|
||||
|
||||
We pledge to act and interact in ways that contribute to an open, welcoming,
|
||||
diverse, inclusive, and healthy community.
|
||||
|
||||
## Our Standards
|
||||
|
||||
Examples of behavior that contributes to a positive environment for our
|
||||
community include:
|
||||
|
||||
* Demonstrating empathy and kindness toward other people
|
||||
* Being respectful of differing opinions, viewpoints, and experiences
|
||||
* Giving and gracefully accepting constructive feedback
|
||||
* Accepting responsibility and apologizing to those affected by our mistakes,
|
||||
and learning from the experience
|
||||
* Focusing on what is best not just for us as individuals, but for the
|
||||
overall community
|
||||
|
||||
Examples of unacceptable behavior include:
|
||||
|
||||
* The use of sexualized language or imagery, and sexual attention or
|
||||
advances of any kind
|
||||
* Trolling, insulting or derogatory comments, and personal or political attacks
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or email
|
||||
address, without their explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a
|
||||
professional setting
|
||||
|
||||
## Enforcement Responsibilities
|
||||
|
||||
Community leaders are responsible for clarifying and enforcing our standards of
|
||||
acceptable behavior and will take appropriate and fair corrective action in
|
||||
response to any behavior that they deem inappropriate, threatening, offensive,
|
||||
or harmful.
|
||||
|
||||
Community leaders 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, and will communicate reasons for moderation
|
||||
decisions when appropriate.
|
||||
|
||||
## Scope
|
||||
|
||||
This Code of Conduct applies within all community spaces, and also applies when
|
||||
an individual is officially representing the community in public spaces.
|
||||
Examples of representing our community include using an official e-mail address,
|
||||
posting via an official social media account, or acting as an appointed
|
||||
representative at an online or offline event.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported to the community leaders responsible for enforcement at
|
||||
[@lawnchairapp](https://twitter.com/lawnchairapp), [Telegram](https://t.co/qYev4OkvpT), or [Discord](https://discord.com/invite/3x8qNWxgGZ).
|
||||
All complaints will be reviewed and investigated promptly and fairly.
|
||||
|
||||
All community leaders are obligated to respect the privacy and security of the
|
||||
reporter of any incident.
|
||||
|
||||
## Enforcement Guidelines
|
||||
|
||||
Community leaders will follow these Community Impact Guidelines in determining
|
||||
the consequences for any action they deem in violation of this Code of Conduct:
|
||||
|
||||
### 1. Correction
|
||||
|
||||
**Community Impact**: Use of inappropriate language or other behavior deemed
|
||||
unprofessional or unwelcome in the community.
|
||||
|
||||
**Consequence**: A private, written warning from community leaders, providing
|
||||
clarity around the nature of the violation and an explanation of why the
|
||||
behavior was inappropriate. A public apology may be requested.
|
||||
|
||||
### 2. Warning
|
||||
|
||||
**Community Impact**: A violation through a single incident or series
|
||||
of actions.
|
||||
|
||||
**Consequence**: A warning with consequences for continued behavior. No
|
||||
interaction with the people involved, including unsolicited interaction with
|
||||
those enforcing the Code of Conduct, for a specified period of time. This
|
||||
includes avoiding interactions in community spaces as well as external channels
|
||||
like social media. Violating these terms may lead to a temporary or
|
||||
permanent ban.
|
||||
|
||||
### 3. Temporary Ban
|
||||
|
||||
**Community Impact**: A serious violation of community standards, including
|
||||
sustained inappropriate behavior.
|
||||
|
||||
**Consequence**: A temporary ban from any sort of interaction or public
|
||||
communication with the community for a specified period of time. No public or
|
||||
private interaction with the people involved, including unsolicited interaction
|
||||
with those enforcing the Code of Conduct, is allowed during this period.
|
||||
Violating these terms may lead to a permanent ban.
|
||||
|
||||
### 4. Permanent Ban
|
||||
|
||||
**Community Impact**: Demonstrating a pattern of violation of community
|
||||
standards, including sustained inappropriate behavior, harassment of an
|
||||
individual, or aggression toward or disparagement of classes of individuals.
|
||||
|
||||
**Consequence**: A permanent ban from any sort of public interaction within
|
||||
the community.
|
||||
|
||||
## Attribution
|
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
||||
version 2.0, available at
|
||||
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
|
||||
|
||||
Community Impact Guidelines were inspired by [Mozilla's code of conduct
|
||||
enforcement ladder](https://github.com/mozilla/diversity).
|
||||
|
||||
[homepage]: https://www.contributor-covenant.org
|
||||
|
||||
For answers to common questions about this code of conduct, see the FAQ at
|
||||
https://www.contributor-covenant.org/faq. Translations are available at
|
||||
https://www.contributor-covenant.org/translations.
|
||||
13
SECURITY.md
Normal file
13
SECURITY.md
Normal file
@@ -0,0 +1,13 @@
|
||||
# Security Policy
|
||||
|
||||
## Supported Versions
|
||||
Important note: Lawnchair v2 (Play Store version) is **unsupported**. Use the newer alphas instead. See [this FAQ page](https://github.com/LawnchairLauncher/lawnchair/wiki/FAQ#do-you-still-support-the-play-store-version) for additional information.
|
||||
|
||||
The latest version of Lawnchair is the only supported version.
|
||||
| Version | Supported |
|
||||
| ------- | ------------------ |
|
||||
| 12.1 | :white_check_mark: |
|
||||
| 12 | :x: |
|
||||
| 11 | :x: |
|
||||
| v2 | :x: |
|
||||
| v1 | :x: |
|
||||
Reference in New Issue
Block a user