Labels
Labels
38 labels
- Pull requests that update a dependency file
- Submitter still working on, is draft, or appears inclomplete
- Subdomain providers must have an easily discoverable abuse contact on their website.
- Pull requests that update Go code
- (historical) Marked as approved and ready to merge by @sleevi
- collateral damage of privacy/surveillance standards needing a band-aid fix via FOSS volunteers
- PR related to Issue #1245 / needs https://www.facebook.com/help/contact/474057987130813
- This is a PR that might benefit from a re-review
- Will need requestor email domain and company domain(s) to have _psl txt of PR URL in DNS
- Alteration to code/automation or publicsuffix.org site
- Submitter attests PR is not #1245 related
- Marked as approved and ready to merge by @dnsguru
- Pull Requests marked for mergeing by @mozfreddyb
- Marked as approved and ready to merge by @simon-friedberger
- Marked as approved and ready to merge by @weppos
- Tasks we're voluntelling you what would help us.
- Blocked for need of follow-up
- Automation pull from Authoritative ICANN json source
- RFC 8553 Entries were present, matching PR#
- https://github.com/publicsuffix/list/wiki/Guidelines#sort-your-submission-correctly-important
- 3rd party suggesting that the PSL is solution to x is typically a rejection scenario. Explain more.
- Unable to confirm _PSL TXT = This PR # (also see #1439)
- *ALL* names in PRIVATE section MUST hold terms of 2 years or more registration from PR date #1109
- https://github.com/publicsuffix/list/wiki/Guidelines#sort-your-submission-correctly-important
- A required acceptance criteria is to run the tests when submitting a PR
- See https://github.com/publicsuffix/list/wiki/Guidelines#validation-and-non-acceptance-factors
- Got out of synch with the repo and needs a re-base on it
- PR stand as transparency records; Guidelines require longer description and/or rationale.
- Invalid Pull Request Template Used (see https://github.com/publicsuffix/list/issues/2612 )