Hi everyone

I just got Fairy to set labels, this requires a custom GCLI (yes, i will submit 
the fix upstream)

First PR where we set labels: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22936

Label prompt:

        "Label: important, should be set for crash, security, ... fixes, and 
also major features that a lot of users would want or benefit from. It should 
not be set for source level UB like integer overflows in dsp code\n"
        "Label: enhancement, should be set for PRs that add a feature\n"
        "Label: fix/bug, should be set for PRs that fix a bug\n"
        "Label: fix/regression, should be set for PRs that fix a regression\n"
        "Label: invalid, should be set for PRs/issues that arent valid 
PRs/issues, like jokes, trolls, spam\n"
        "Label: API, Introduces new API that warants a minor bump\n"
        "Label: API major, Changes the API in a major way, needing a major 
bump\n"
        "Label: needs sample, should be set when reproducing or testing the 
change requires a sample file the submitter has not provided\n"
        "Label: needs docs, should be set when the PR adds user-visible 
behavior or API that lacks the matching documentation update\n"
        "Label: needs testing, should be set when the PR needs additional 
testing (FATE coverage, fuzzing, on-device runs) before it can be merged, this 
is unrelated to CI failures\n"
        "Label: duplicate, should be set for PRs/issues that duplicate an 
already-open or already-resolved PR/issue\n"

If you guys have additions to this tell me!

I dont plan to brute force run fairy over every PR to set labels yet
ATM she will just fix labels as a side effect

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Elect your leaders based on what they did after the last election, not
based on what they say before an election.

Attachment: signature.asc
Description: PGP signature

_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to