Git hub pull request1/20/2024 ![]() This will also repeat the verification.Īll pull requests are subject to CI runs that run pkgcheck on the whole repository. When the submitter fixes the issue, or the package list changes, you can remove the assigned label in order to force reassignment. If an unregistered address is found, the assignment comment contains a verbose warning about it. The assignment script additionally verifies that the e-mail addresses of the maintainers are registered on the Gentoo Bugzilla. ![]() The script will automatically remove the previous assignment comment. In order to have the pull request re-assigned, remove all assignees (if any) and the appropriate label. In order to prevent automatic assignment, please set the assigned label or add at least one explicit assignee. If the script was able to find at least one assignee for each of the modified packages, the pull request is marked assigned. Packages whose maintainers have no GitHub account (as in, none of the maintainers do have one) are marked as non-assignable. ![]() Pull requests involving packages with more than 5 unique sets of maintainers are not assigned automatically (to prevent spam).Eclass and profile changes are not assigned automatically, and instead assumed to be handled by other assignees of the pull request (if any).New and unmaintained packages are assigned to Project:Proxy Maintainers as candidates for proxy maintenance.It should be noted that the files from the current ::gentoo version are used rather than ones from the pull request. The script reads the current maintainers from the metadata.xml files, and maps them to GitHub developers/teams. The assignment is performed based on the list of changed files. The assignment script leaves a comment appropriate developers/teams and setting labels appropriately. The new pull requests are automatically assigned using a cronjob run every 4 minutes.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |