Add Backport Usage

[lizard-boy]

🎟️ Tracking

📔 Objective

Depends on bitwarden/gh-actions#305

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

Greptile Summary

Added a new workflow file 'backport.yml' to automate the process of backporting pull requests based on issue comments.

• Introduced .github/workflows/backport.yml to handle automated backporting of PRs
• Utilizes a reusable workflow from bitwarden/gh-actions repository
• Configures permissions for contents, issues, pull requests, and actions
• Defines a custom PR description template for backported PRs

[greptile-apps]

_{1 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: Permissions seem overly broad. Review and restrict to only necessary scopes

[greptile-apps]

style: Remove or update the comment 'My Draft PR:' as it's not informative in the final version