├── .github ├── ISSUE_TEMPLATE.md └── move.yml ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md └── README.md /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 14 | 15 | ### Short description of the issue 16 | 17 | Short description goes here. 18 | 19 | ### Expected behavior 20 | 21 | Expected behavior goes here. 22 | 23 | ### Actual behavior 24 | 25 | Actual behavior goes here. 26 | 27 | ### Optional: Screenshots/Links that demonstrate the issue 28 | 29 | Your screenshots/links go here. 30 | 31 | ### Optional: Suggestion for a possible fix 32 | 33 | Your possible fix goes here. 34 | 35 | ### Steps to reproduce the issue 36 | 37 | 38 | 1. Step 1 39 | 2. Step 2 40 | 3. Step 3 41 | 42 | ### Setup/Environment 43 | 47 | 48 | * ProcessWire version: 49 | * (Optional) PHP version: 50 | * (Optional) MySQL version: 51 | * (Optional) Any 3rd party modules that are installed and could be related to the issue: 52 | -------------------------------------------------------------------------------- /.github/move.yml: -------------------------------------------------------------------------------- 1 | # Configuration for move-issues - https://github.com/dessant/move-issues 2 | 3 | # Delete the command comment when it contains no other content 4 | deleteCommand: true 5 | 6 | # Close the source issue after moving 7 | closeSourceIssue: true 8 | 9 | # Lock the source issue after moving 10 | lockSourceIssue: false 11 | 12 | # Mention issue and comment authors 13 | mentionAuthors: true 14 | 15 | # Preserve mentions in the issue content 16 | keepContentMentions: false 17 | 18 | # Set custom aliases for targets 19 | aliases: 20 | requests: processwire/processwire-requests 21 | 22 | # Repository to extend settings from 23 | # _extends: repo 24 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | 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, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others’ private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | 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. 28 | 29 | 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. 30 | 31 | ## Scope 32 | 33 | 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. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [github@processwire.com](mailto:github@processwire.com). 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. 38 | 39 | 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. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org/), version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4). 44 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to the ProcessWire issues repository 2 | 3 | Thank you for taking the time to identify issues in ProcessWire. :+1: 4 | 5 | We manage issues from this separate repository so that we can maintain a collaborative team to assist with issue reports. The following is a set of guidelines for contributing to this repository. These are just guidelines, not rules, use your best judgment and feel free to propose changes to this document in a [pull request](https://github.com/processwire/processwire-issues/pulls). 6 | 7 | ## Code of conduct 8 | 9 | This project adheres to the Contributor Covenant [code of conduct](https://github.com/processwire/processwire-issues/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [github@processwire.com](mailto:github@processwire.com). 10 | 11 | ## Before submitting a bug report 12 | 13 | There is a good chance that you don’t need to create a bug report in the first place. Please check the following list: 14 | 15 | * When possible please **confirm the issue on a separate installation** before submitting an issue report. 16 | * Please **do not submit feature requests**, instead use the [requests repository](https://github.com/processwire/processwire-requests/issues). 17 | * Please **do not use this repository for ProcessWire support**, instead use the [support forum](https://processwire.com/talk/). 18 | * **Check the [FAQs on the forum](https://processwire.com/talk/forum/6-faqs/)** for a list of common questions and problems. 19 | * **Perform a [cursory search](https://github.com/issues?utf8=✓&q=is%3Aissue+repo%3Aprocesswire%2Fprocesswire-issues)** to see if the problem has already been reported. If it has, add a comment to the existing issue instead of opening a new one. 20 | 21 | ## How to submit a (good) bug report 22 | 23 | Always include as many details as possible. There is an [issue template](https://github.com/processwire/processwire-issues/blob/master/.github/ISSUE_TEMPLATE.md) which gets used automatically when you create a new issue. Please use it as it contains all the information needed for a good bug report. 24 | 25 | This will help maintainers and the community understand your report, reproduce the behavior, find related reports, and get to a solution more quickly and efficiently. 26 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # ProcessWire Issue Reports 2 | 3 | Thank you for helping to identify issues in ProcessWire. We manage issues from this separate 4 | repository so that we can maintain a collaborative team to assist with issue reports. 5 | 6 | - Submit ProcessWire issue reports to the issues repository: 7 | [processwire-issues](https://github.com/processwire/processwire-issues/issues) 8 | 9 | - Please do not submit feature requests to the issues repository, instead use the requests repository: 10 | [processwire-requests](https://github.com/processwire/processwire-requests/issues) 11 | 12 | - Please do not use the issues repository for ProcessWire support, instead use the support forum: 13 | 14 | 15 | - Always include the full ProcessWire version (i.e. 3.0.34). Also include the PHP or MySQL version 16 | when potentially applicable. 17 | 18 | - Indicate any 3rd party modules that are installed. 19 | 20 | - When possible please confirm the issue on a separate installation before submitting 21 | an issue report. 22 | 23 | - When the issue is resolved, please close it. 24 | 25 | --------------------------------------------------------------------------------