Skip to content

reactor actually explode option #752

reactor actually explode option

reactor actually explode option #752

Workflow file for this run

name: Pull Request Labels
on:
pull_request_target:
types:
- opened
permissions:
contents: read
pull-requests: write
jobs:
pr-labeler:
name: Pull Request Labels
runs-on: ubuntu-latest
if: github.repository == 'Slimefun/Slimefun4'
steps:
- uses: baked-libs/[email protected]
id: labeller
name: Apply labels based on branch
with:
token: "${{ secrets.GITHUB_TOKEN }}"
renovate: '🚨 Dependency Update'
crowdin: '📄 Translations Update'
feature: '🎈 Feature'
fix: '✨ Fix'
chore: '🧹 Chores'
performance: '💡 Performance Optimization'
api: '🔧 API'
compatibility: '🤝 Compatibility'
- uses: thollander/[email protected]
name: Leave a comment about the applied label
if: ${{ steps.labeller.outputs.applied != 0 }}
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
message: |
Your Pull Request was automatically labelled as: "${{ steps.labeller.outputs.applied }}"
Thank you for contributing to this project! ❤️
- uses: thollander/[email protected]
name: Leave a comment about our branch naming convention
if: ${{ steps.labeller.outputs.applied == 0 }}
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
message: |
**Pro Tip!**
You can help us label your Pull Requests by using the following branch naming convention next time you create a pull request. ❤️
Branch naming convention | Label
------------------------ | ------
`feature/**` | 🎈 Feature
`fix/**` | ✨ Fix
`chore/**` | 🧹 Chores
`api/**` | 🔧 API
`performance/**` | 💡 Performance Optimization
`compatibility/**` | 🤝 Compatibility
<hr>
If your changes do not fall into any of these categories, don't worry.
You can just ignore this message in that case! 👀