docs(.github): added pull request template for ui components repo

[rax7389]

Changes

Please describe both what is changing and why this is important. Include:

Added .github/pull_request_template.md to standardize description requirements for all Pull Requests submitted to the UI components repository.

Testing

It does not have any test or coverage added because it is a .md file

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All existing and new tests complete without errors

[github-actions]

🚀 Preview deployment

Branch: refs/pull/43/merge
Commit: f6e74ad

📝 Preview URL: https://auth0-universal-components-nfr0vcq9p-okta.vercel.app

---

Updated at 2025-12-22T12:48:14.429Z

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.13%. Comparing base (a3693d5) to head (1a67bc3).

Additional details and impacted files

@@           Coverage Diff            @@
##             main      #43    +/-   ##
========================================
  Coverage   83.13%   83.13%            
========================================
  Files         125      125            
  Lines       10262    10262            
  Branches     1262     1007   -255     
========================================
  Hits         8531     8531            
  Misses       1731     1731            

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[grandmaester]

LGTM!!

[NaveenChand755]

shall we include the below to make it easier for the reviewer and to show intent of the change

Type of change

Please check the relevant option:

• Feature (new functionality)
• Bug fix (fixes an issue)
• Refactor (no functional change)
• Chore (maintenance, tooling, docs)

[rax7389]

shall we include the below to make it easier for the reviewer and to show intent of the change

Type of change

Please check the relevant option:

• Feature (new functionality)
• Bug fix (fixes an issue)
• Refactor (no functional change)
• Chore (maintenance, tooling, docs)

as discussed we will have title of the PR to indicate the type of change the PR might have, going further lets standardize it with a help of a pipeline to check and block the PR