bevy/.github/label-config.yml

# Config for the label workflow
# Schema: https://github.com/actions/labeler#create-githublabeleryml

S-Needs-Triage:
- "**"

S-Pre-Relicense:
- "**"
Relicense bors checks (#2493) # Objective Currently we can sometimes allow PRs by people who haven't agreed to the relicense to get merged into main. E.g. https://github.com/bevyengine/bevy/pull/2445 ## Solution This adds a check to ensure that this doesn't happen, by ensuring that bors doesn't relicense said PRs. As a bonus, it also adds config to automatically label new PRs as needing checking, to ensure that we do the verification until we merge the new license. 2021-07-17 18:56:56 +00:00			`# Config for the label workflow`
			`# Schema: https://github.com/actions/labeler#create-githublabeleryml`

label config: change needs-triage to S-Needs-Triage 2021-07-13 20:27:14 +00:00			`S-Needs-Triage:`
Automated PR labeling (#2301) # Objective - Currently only issues automatically have labels assigned to them on creation. - The enables pull requests to have the same functionality and currently only adds the `needs-triage` label to all PRs. ## Solution - Integrate `actions/labeler@v2` into the github workflows to automatically tag PRs. - Add a `label-config.yml` file that specifies how PRs should be labeled. 2021-06-07 20:53:27 +00:00			`- "**"`
Relicense bors checks (#2493) # Objective Currently we can sometimes allow PRs by people who haven't agreed to the relicense to get merged into main. E.g. https://github.com/bevyengine/bevy/pull/2445 ## Solution This adds a check to ensure that this doesn't happen, by ensuring that bors doesn't relicense said PRs. As a bonus, it also adds config to automatically label new PRs as needing checking, to ensure that we do the verification until we merge the new license. 2021-07-17 18:56:56 +00:00
			`S-Pre-Relicense:`
			`- "**"`