Lines Matching full:issues
18 and linked to any relevant :ref:`bug or feature tracking issues<bug_reporting>`
125 - Hot fixes: Fixing CI issues, reverts, and system breakage
172 - Can you fix unrelated issues
175 Closing Stale Issues and Pull Requests
178 - The Pull requests and issues sections on Github are NOT discussion forums.
181 - In case of both issues and pull-requests the original poster needs to respond
199 Developers are expected to fix issues and rework their patches and submit again.
203 - Run ``checkpatch`` for code style issues (can vote -1 on errors; see note)
217 accurately. As such it sometimes issues false positives. Known
237 Labeling issues and pull requests in GitHub
240 The project uses GitHub issues and pull requests (PRs) to track and manage
242 GitHub **labels** to classify and organize these issues and PRs by area, type,
245 All GitHub issues or pull requests must be appropriately labeled.
246 Issues and PRs often have multiple labels assigned,
256 Labels applicable to issues only
294 - Issues that need to be mentioned in release notes as known issues with
337 - The PR has licensing issues which require a licensing expert to review it.
345 Labels applicable to both pull requests and issues
360 An area maintainer should be able to filter by an area label and find all issues
399 - For PRs: is work in progress and should not be merged yet. For issues: Is being