Add .github folder

- Add Issue templates
- Add Pull request
- Add Code of conduct
- Add Contributing
- Add Security

Author: prod3v3loper

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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. 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][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTING.md

@@ -0,0 +1,85 @@
+# Contributing
+
+> I welcome feature requests and bug reports. Please read these guidelines before submitting one.
+
+From opening a bug report to creating a pull request: every contribution is appreciated and welcomed.
+
+# Your first Contribution
+
+First of all, you will need to create an issue in Github for the feature or bugfix that you want to work on. When you open a new issue, there will be a template that will be automatically added to the text of the issue, which you would need to fill in. Doing this will help us to understand better what the ticket is about.
+
+After you've created the issue, we will have a look, and provide feedback to your ticket.
+
+In case it is a bug that you want to fix, we might help you with background information about the issue, so you can make an informed fix.
+
+Words that begin with the at sign (@) must be wrapped in backticks! . As a courtesy to avoid sending notifications to any user that might have the @username being referenced, please remember that GitHub usernames also start with the at sign. 
+
+If you don't wrap them in backticks, users will get unintended notifications from you.
+
+In case you are suggesting a new feature, we will match your idea with our current roadmap, and will open conversations about it. Once the discussion has been done, and the tasks cleared, then you're ready to code.
+
+GitHub has other great markdown features as well, go [here](https://help.github.com/categories/writing-on-github/) to learn more about them.
+
+# Reporting Issues
+
+Most of the time, when webpack does not work correctly, it might be a configuration issue.
+
+If you are still having difficulty after looking over your configuration carefully, please post a question to [StackOverflow with the MVC tag](http://stackoverflow.com/tags/autoloader). This way you help others to help you.
+
+> You should also have Google search and other plattforms included.
+
+**If you have discovered a bug or have a feature suggestion, feel free to create an issue on Github.**
+
+It can happen again and again that mistakes have crept in and the code does not work smoothly. That's why you can open a ticket here and get help. However, it should be checked beforehand if someone already had this error and he was already helped.
+
+### Creating branch
+
+Making a branch in your fork for your contribution is helpful in the following ways:
+
+* It allows you to submit more than one contribution in a single PR.
+* It allows us to identify what your contribution is about from the branch name.
+
+You will want to checkout the `main` branch locally before creating your new branch.
+
+There are two types of branches:
+
+* Feature
+* Bugfix
+
+### Features
+
+If your contribution is something new, like an option for the cli, you can create a branch with the following prefix:
+
+`feature/<the-new-feature>`
+
+### Fixes
+
+If you are fixing an existing bug, you can create a branch with the following prefix:
+
+`bugfix/<the-fix>`
+
+### Testing
+
+Any bug fix or feature you submit needs to be tested. Writing tests for code is very important to avoid future errors and to immediately detect potential new errors.
+
+It's important that you test the logic of the code you're writing, and that your tests really go through all the lines, branches, and instructions. Only in this way can it be ensured that the code coverage is high enough to ensure that the users of the generator use a solid tool.
+
+If you need help or need advice on writing your tests, please contact us. We would like to point you in the right direction.
+
+Write here your [issues](https://github.com/prod3v3loper/php-auto-autoloader/issues).
+
+# Pull Requests
+
+After receiving some feedback, press down on your fork and submit a pull request. We can suggest some changes, improvements or implementation alternatives.
+
+Create a new industry as described above.
+
+If you made a small change in most cases, your pull request will be accepted faster.
+
+### Submitting a good Pull Request
+
+* Test before submit
+* Follow our code convention
+* Write a good commit message
+
+Show all [pulls](https://github.com/prod3v3loper/php-auto-autoloader/pulls).

.github/ISSUE_TEMPLATE/BUG_REPORT.yml

@@ -0,0 +1,71 @@
+name: Bug Report
+description: Report a bug
+title: "[Bug]: "
+labels: ["bug", "triage"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+
+  - type: input
+    attributes:
+      label: Contact Details
+      description: |
+        How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: What happened?
+      description: |
+        Also tell us, what did you expect to happen?
+      placeholder: A bug happened! Tell us what happend?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Steps to reproduce the behavior!
+      description: |
+        A clear and concise description of what you expected to happen.
+      value: "1. Go to '...'
+        2. Click on '....'
+        3. Scroll down to '....'
+        4. See error"
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Device and information
+      description: |
+        A description of your device and their informations
+      value: "- OS: [e.g. iOS]
+        - Browser [e.g. chrome, safari]
+        - Version [e.g. 22]
+        - Device: [e.g. iPhone6]"
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. 
+        This will be automatically formatted into code, so no need for backticks.
+      render: bash
+    validations:
+      required: false
+
+  - type: checkboxes
+    attributes:
+      label: Code of Conduct
+      description: |
+        By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/prod3v3loper/php-auto-autoloader/blob/main/.github/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.yml

@@ -0,0 +1,63 @@
+name: Feature Request
+description: Suggest an idea to help us improve
+title: "[Feature]: "
+labels: ["feature", "enhancement"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this feature request!
+
+  - type: input
+    attributes:
+      label: Contact Details
+      description: |
+        How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Description of feature!
+      description: |
+        Is your feature request related to a problem?
+        A clear and concise description of what the problem is.
+      placeholder: Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Suggested Solution
+      description: |
+        Describe the solution you'd like!
+        A clear and concise description of what you want to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Alternatives
+      description: |
+        Describe alternatives you've considered.
+        A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Additional Context
+      description: |
+        Add any other context about the problem here.
+    validations:
+      required: false
+
+  - type: checkboxes
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/prod3v3loper/php-auto-autoloader/blob/main/.github/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/PULL_REQUEST_TEMPLATE/pull_request.md

@@ -0,0 +1,40 @@
+# Description
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+
+Fixes # (issue)
+
+## Type of change
+
+Please fill options that are relevant with [x].
+
+- [ ] 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)
+- [ ] This change requires a documentation update
+
+# How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
+
+- [ ] Test A
+- [ ] Test B
+
+**Test Configuration**:
+* Node version:
+* NPM version:
+* Webpack version:
+* Yeoman version:
+
+# Checklist
+
+Please fill in everything that was done
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules

.github/SECURITY.md

@@ -0,0 +1,16 @@
+# Security Policy
+
+## Supported Versions
+
+We only support the latest version.
+
+| Version        | Supported          |
+| -------------- | ------------------ |
+| x.x.x latest   | :white_check_mark: |
+| 5.0.x          | :x:                |
+| 4.0.x          | :x:                |
+| < 4.0          | :x:                |
+
+## Reporting a Vulnerability
+
+For more information lokk at [GitHub docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability).