Adhere to GitHub Community Standards

[alganet]

Makes the project more friendly to GitHub users by providing conventional files.

Those changes will improve our score under the GitHub community tab:

https://github.com/Respect/Validation/community

• The CONTRIBUTING.md file was moved to the .github/ folder to remove clutter. This change is also in preparation to create more comprehensive developer documentation under a dedicated section in docs/
• The CHANGELOG.md file was removed. It was outdated and not being maintained.
• Minimalistic .github/PULL_REQUEST_TEMPLATE.md
• Minimalistic .github/SECURITY.md
• Minimalistic .github/CODE_OF_CONDUCT.md
• Minimalistic .github/ISSUE_TEMPLATES

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.93%. Comparing base (d1d8980) to head (b67bcb0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #1625   +/-   ##
=========================================
  Coverage     97.93%   97.93%           
  Complexity      958      958           
=========================================
  Files           197      197           
  Lines          2228     2228           
=========================================
  Hits           2182     2182           
  Misses           46       46           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

This PR improves the project's GitHub community standards compliance by adding standard GitHub community files and reorganizing existing documentation.

Changes:

• Moved CONTRIBUTING.md to .github/ folder and updated the reference in README.md
• Removed outdated CHANGELOG.md file
• Added GitHub community standard files: SECURITY.md, PULL_REQUEST_TEMPLATE.md, CODE_OF_CONDUCT.md, and issue templates

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
REUSE.toml	Updated copyright annotations to include new GitHub template files
README.md	Updated link to point to relocated CONTRIBUTING.md in .github/ folder
CHANGELOG.md	Removed outdated changelog file that was no longer maintained
.github/SECURITY.md	Added security policy with vulnerability reporting instructions
.github/PULL_REQUEST_TEMPLATE.md	Added minimalistic pull request template with type of change checklist
.github/ISSUE_TEMPLATES/feature_request.md	Added feature request issue template
.github/ISSUE_TEMPLATES/bug_report.md	Added bug report issue template
.github/CONTRIBUTING.md	Relocated contributing guidelines from root to .github/ folder
.github/CODE_OF_CONDUCT.md	Added minimalistic code of conduct

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[henriquemoody]

This is an awesome change!

Most of those files can stay at the root of the repository and still adhere to GitHub's community standards. I was seeing that other projects also leave them at the root:

https://github.com/symfony/symfony
https://github.com/doctrine/orm
https://github.com/composer/composer/

[alganet]

@henriquemoody

I, personally, don't like these files very much. That's why I'm adding them to the .github folder. I see them as interfaces to the GitHub workflow, not actual docs.

As I mentioned in the commit description, my plan is to have a docs/development folder with richer information that we can link .github -> docs when needed, keeping the mandatory files to score high according to GitHub very short.

Do you prefer them in the root folder? I find that to add too much clutter, with UPPERCASED files that are too distracting.

[henriquemoody]

Personally, I tend to look at the CONTRIBUTING.md file in repositories, and I think some AI agents also look for them.

If you feel strongly about having all those files at the root, I can compromise with all of them, but I would really want to keep the CONTRIBUTING.md file in the root folder.

[henriquemoody]

I don't mid the uppercase files because LICENSE and README are also standard, and they're uppercase. More of the same to mee

[alganet]

@henriquemoody makes sense, I moved the CONTRIBUTING.md file back.

[henriquemoody]

You gotta edit your commit message, BTW