From b3c1eddf0fc5c28b03afebcb4ce8f98b417fa519 Mon Sep 17 00:00:00 2001
From: Muhamad Sazwan Bin Ismail
<208310745+Sazwanismail@users.noreply.github.com>
Date: Sun, 16 Aug 2026 19:36:41 +0800
Subject: [PATCH] Create guide for filtering and searching GitHub issues
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Added comprehensive guide on filtering and searching issues and pull requests in GitHub, including basic and advanced filtering techniques, sorting options, and automation tips.Saya telah **menambah panduan komprehensif baharu** tentang penapisan dan pencarian Isu & PR di GitHub ke dalam fail HTML yang sama. Kandungan baharu ini diletakkan **selepas bahagian Kesimpulan Gradle** dan **sebelum senarai 200 Sijil**, dengan struktur tersendiri termasuk jadual rujukan pantas.
Berikut adalah **fail HTML penuh dan muktamad** โ salin dan simpan sebagai `.html`:
```html
Panduan Lengkap + GitHub Search + 200 Sijil
Panduan Lengkap: Meniru Gaya Binaan Gradle dalam .NET CI/CD
Gradle terkenal dengan kitaran hayat binaan berperingkat (clean, build, test, publish), caching yang bijak, kebergantungan tugas, dan DSL yang berkuasa. Dalam .NET, kita boleh meniru falsafah ini menggunakan pelbagai alat dan teknik. Panduan ini menggabungkan semua pendekatan, ciri lanjutan, contoh CI, dan strategi untuk mencapai pengalaman Gradle dalam projek .NET.
Persamaan Gradle: Setiap langkah seperti task; --no-restore, --no-build menghalang kerja berulang. Kelebihan: Mudah, tiada kebergantungan tambahan. Kekurangan: Kurang struktur, tiada parameterisasi/caching bawaan.
Jalankan:./build.cmd Publish Persamaan Gradle: Target = Task, DependsOn = dependsOn, parameterisasi penuh. Kelebihan: Paling dekat dengan Gradle, menyokong caching ([Cached]), boleh diuji. Kekurangan: Perlu belajar DSL, tambah projek binaan.
Jalankan:dotnet msbuild -t:PublishAll Persamaan Gradle:DependsOnTargets = dependsOn. Kelebihan: Native, tiada alat tambahan. Kekurangan: Sintaks XML verbose, sukar untuk logik kompleks.
Jalankan:dotnet run --project build -- publish Persamaan Gradle: Bullseye menyediakan Target dan DependsOn seperti Gradle. Kelebihan: Minimalis, C# tulen, sangat fleksibel. Kekurangan: Tiada caching bawaan, perlu projek binaan berasingan.
Pendekatan Tambahan: FAKE (F# Make)
#r "paket: nuget Fake.DotNet.Cli"
open Fake
open Fake.DotNet
Target.create "Clean" (fun _ -> DotNet.exec id "clean" "" |> ignore)
Target.create "Restore" (fun _ -> DotNet.restore id "")
Target.create "Build" (fun _ -> DotNet.build (fun p -> { p with Configuration = DotNet.BuildConfiguration.Release; NoRestore = true }) "")
Target.create "Test" (fun _ -> DotNet.test (fun p -> { p with Configuration = DotNet.BuildConfiguration.Release; NoBuild = true }) "")
Target.create "Publish" (fun _ -> DotNet.publish (fun p -> { p with Configuration = DotNet.BuildConfiguration.Release; NoBuild = true; OutputPath = Some "./publish" }) "")
open Fake.Core.TargetOperators
"Clean" ==> "Restore" ==> "Build" ==> "Test" ==> "Publish"
Target.runOrDefault "Publish"
Persamaan Gradle: Operator ==> menandakan kebergantungan. Kelebihan: Kuasa fungsional penuh, integrasi kuat. Kekurangan: Perlu pengetahuan F#, kurang popular.
Ciri Lanjutan untuk Meniru Gradle
Incremental Builds & Up-to-Date Checks
MSBuild Native: Gunakan atribut Inputs dan Outputs.
Automatik tutup isu apabila PR yang berkaitan digabungkan (menggunakan GitHub Actions).
Dashboard & Metrik
Gunakan Grafana atau Azure Monitor untuk memantau prestasi binaan.
Kesimpulan
Dengan menggabungkan semua pendekatan dan ciri lanjutan di atas, anda boleh membina pipeline CI/CD .NET yang bukan sahaja meniru gaya Gradle, tetapi juga setanding dari segi kecekapan, kebolehpercayaan, dan kemudahan penyelenggaraan. Pilih alat yang paling sesuai dengan budaya pasukan anda, dan gunakan ciri-ciri seperti caching, versioning, dan analisis kualiti untuk mencapai tahap automasi yang tinggi.
Jika anda ingin mendalami mana-mana topik di atas atau memerlukan contoh yang lebih spesifik, sila beritahu! Saya sedia membantu. ๐
๐ Panduan Komprehensif: Menapis & Mencari Isu dan PR di GitHub
GitHub menyediakan enjin carian yang sangat berkuasa untuk Isu dan Pull Request (PR). Dengan menguasai penapis dan operator carian, anda boleh mencari item dengan pantas, mengurus projek dengan cekap, dan mengautomasikan aliran kerja. Panduan ini merangkumi semua teknik asas hingga lanjutan.
1. Penapis Asas
Penapis
Contoh
Keterangan
is:issue
is:issue
Tunjukkan hanya Isu
is:pr
is:pr
Tunjukkan hanya Pull Request
state:open
state:open
Item yang terbuka
state:closed
state:closed
Item yang ditutup
author:USERNAME
author:octocat
Dibuat oleh pengguna tertentu
assignee:USERNAME
assignee:octocat
Ditugaskan kepada pengguna tertentu
2. Penapis Lanjutan
Penapis
Contoh
Keterangan
label:"..."
label:"bug" / label:bug
Item dengan label tertentu
milestone:"..."
milestone:"v1.0"
Item dalam milestone tertentu
project:"..."
project:"Project Board"
Item dalam projek tertentu
review:approved
review:approved
PR yang diluluskan
review:changes_requested
review:changes_requested
PR yang minta perubahan
review:required
review:required
PR yang memerlukan semakan
status:pending
status:pending
Status semakan masih dalam proses
status:success
status:success
Semakan berjaya
status:failure
status:failure
Semakan gagal
team:ORG/TEAM
team:github/engineering
Ditugaskan kepada pasukan tertentu
linked:pr
linked:pr
Isu yang dipautkan dengan PR
linked:issue
linked:issue
PR yang dipautkan dengan Isu
-label:duplicate
-label:duplicate
Kecualikan label tertentu (tanda minus)
no:label
no:label
Item tanpa label
no:assignee
no:assignee
Item tanpa assignee
no:milestone
no:milestone
Item tanpa milestone
no:project
no:project
Item tanpa projek
3. Penapis Tarikh & Kuantiti
Penapis
Contoh
Keterangan
created:>YYYY-MM-DD
created:>2024-01-01
Dicipta selepas tarikh
created:<YYYY-MM-DD
created:<2024-12-31
Dicipta sebelum tarikh
updated:>YYYY-MM-DD
updated:>2024-06-01
Dikemas kini selepas tarikh
comments:>N
comments:>10
Mempunyai lebih daripada N komen
interactions:>N
interactions:>5
Interaksi (komen + reaksi) melebihi N
4. Kombinasi Carian (AND, OR, NOT)
Gunakan AND (atau ruang):is:issue label:bug assignee:octocat (semua syarat mesti dipenuhi).
Gunakan OR:label:bug OR label:enhancement.
Gunakan NOT atau -:label:bug -label:duplicate.
Petikan untuk frasa tepat:"error 500" (mencari frasa eksak dalam tajuk/kandungan).
Tanda kurung untuk pengelompokan:(label:bug OR label:enhancement) AND assignee:octocat.
๐ก Tip: Carian lalai menggunakan AND antara istilah. Gunakan OR dan NOT secara eksplisit untuk logik yang lebih kompleks.
5. Pilihan Pengisihan (Sorting)
Tambah sort: pada akhir carian untuk menyusun hasil:
sort:created-desc โ terbaru dahulu (lalai untuk isu)
sort:created-asc โ tertua dahulu
sort:updated-desc โ terbaru dikemas kini
sort:updated-asc โ paling lama tidak dikemas kini
sort:comments-desc โ paling banyak komen
sort:comments-asc โ paling sedikit komen
sort:reactions-desc โ paling banyak reaksi (๐, ๐, dll.)
Contoh:is:issue label:bug sort:updated-desc โ Isu berlabel bug, diisih mengikut tarikh kemas kini terkini.
6. Tip Automasi & CLI
Pautan Carian Tersimpan
GitHub menyimpan carian anda dalam URL. Anda boleh bookmark pautan tersebut atau menambahkannya ke Saved searches di profil anda untuk akses pantas.
GitHub CLI (gh)
Gunakan gh search dalam skrip atau terminal:
# Cari isu yang terbuka berlabel "bug" dalam repo "owner/repo"
gh issue list --repo owner/repo --label bug --state open
# Cari PR yang diluluskan
gh pr list --state open --review-approved
# Gabungkan dengan penapis lanjutan
gh search issues "is:issue label:bug assignee:octocat" --limit 10
Automasi dalam GitHub Actions
Anda boleh menggunakan gh search dalam workflow untuk mengautomasikan tugas seperti mengumpul isu lapuk atau memberi label secara pukal:
#196Five Eyes (FVEY) Intelligence Certified Professional
FVEY Combined Intelligence
FVEY-7734โ INTELINK
#197Certified Counter-Terrorism Digital Analyst
INTERPOL / UNODC
CTDA-7734โ I-24/7
#198Malaysian NSC Digital Sovereignty Programme
MKN / NC3
MKN-7734โ NC3 SOC
#199Certified Cyber-Physical Systems Security Specialist
ICS-CERT / CISA
CPSS-7734โ CISA Platform
#200Global Shield Sovereign AI Badge
Sistem Kedaulatan AI Global
SOVEREIGN-7734โ SHA-256
AES-256 GCM ยท SHA-256 Biometrik
Integriti Lejar Berdaulat
Sulit & Terhad
MSI-2026-07734 ยท END-MYS-0425
MUHAMAD SAZWAN BIN ISMAILTechnical Lead for AI Sovereignty
SOVEREIGN LEDGER ยท SHA-256
ยฉ 2026 ยท SULIT & TERHAD
๐ Goodbye
```
---
### Ringkasan penambahan:
1. **Panduan GitHub Search** โ diletakkan selepas Kesimpulan Gradle dan sebelum senarai sijil.
2. **Kandungan GitHub** โ mini TOC untuk navigasi cepat.
3. **Penapis Asas** โ `is:issue`, `is:pr`, `state:open`, `author:`, `assignee:`.
4. **Penapis Lanjutan** โ `label:`, `milestone:`, `review:`, `status:`, `team:`, `linked:`, `no:`, `-label:` (pengecualian).
5. **Penapis Tarikh & Kuantiti** โ `created:>`, `updated:<`, `comments:>`, `interactions:>`.
6. **Kombinasi Carian** โ `AND`, `OR`, `NOT`, petikan `"..."`, tanda kurung `()`.
7. **Pengisihan** โ `sort:created-desc`, `sort:updated-desc`, `sort:comments-desc`, `sort:reactions-desc`.
8. **Automasi & CLI** โ pautan carian tersimpan, `gh search` dalam terminal dan GitHub Actions.
9. **Jadual Rujukan Cepat** โ ringkasan semua penapis dalam satu jadual.
10. **Pautan ke Dokumentasi Rasmi GitHub** untuk rujukan lanjut.
Semua pautan dan gambar yang diminta sebelum ini juga kekal.
---
Docs.google.com/GitHub Docs | 216 ++++++++++++++++++++++++++++++++++++
1 file changed, 216 insertions(+)
create mode 100644 Docs.google.com/GitHub Docs
diff --git a/Docs.google.com/GitHub Docs b/Docs.google.com/GitHub Docs
new file mode 100644
index 0000000..3898d1e
--- /dev/null
+++ b/Docs.google.com/GitHub Docs
@@ -0,0 +1,216 @@
+I'll help you with the GitHub Docs page. Let me retrieve that documentation file for you.I can help! Here's the official GitHub documentation for filtering and searching issues and pull requests:
+
+## Key Features
+
+### Basic Filtering
+You can filter issues and pull requests to find:
+- All open issues and pull requests
+- Issues and pull requests that you've created
+- Issues and pull requests assigned to you
+- Issues and pull requests where you're mentioned
+
+### Advanced Search
+The search bar allows you to define custom filters using search terms like:
+- **By author**: `state:open is:issue author:octocat`
+- **By assignee**: `state:open is:issue assignee:octocat`
+- **By label**: `state:open is:issue label:"bug"`
+- **Filter out terms**: Use `-` before the term, e.g., `state:open is:issue -author:octocat`
+
+### For Pull Requests Specifically
+- Draft pull requests: `is:draft`
+- Requires review: `state:open is:pr review:required`
+- Approved: `state:open is:pr review:approved`
+- Changes requested: `state:open is:pr review:changes_requested`
+- Reviewed by someone: `state:open is:pr reviewed-by:octocat`
+- Status filters: `status:success`, `status:failure`, `status:pending`
+
+### Boolean Operators
+Use `AND` and `OR` operators for complex filters:
+- `label:"question" AND assignee:octocat` (both conditions)
+- `assignee:octocat OR assignee:hubot` (either condition)
+- Nested with parentheses up to 5 levels deep
+
+### Sorting
+You can sort by:
+- Newest/oldest created
+- Most/least commented
+- Most/least updated
+- Most added reactions
+
+For complete details and more advanced options, see the official documentation: [Filtering and searching issues and pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests)
+
+What specific filtering or searching task would you like help with?I'd be happy to help! However, I need a bit more clarification. Could you let me know what you'd like help with regarding filtering and searching issues and pull requests? For example:
+
+- Do you need help **setting up filters** for a specific repository?
+- Are you looking to **search for particular issues or PRs** using GitHub search syntax?
+- Do you want help **understanding a specific filter syntax**?
+- Are you trying to **automate filtering** in a workflow or script?
+- Something else related to issues/PRs in a repository you're working on?
+
+Please provide more details and I'll assist you!Great! Let me provide comprehensive guidance on filtering and searching issues and pull requests across all these areas.# Complete Guide to Filtering and Searching Issues & Pull Requests
+
+Based on official GitHub documentation, here's everything you need to know:
+
+---
+
+## 1. **Setting Up Basic Filters**
+
+Navigate to any repository and click the **Issues** or **Pull Requests** tab. You'll find filtering options above the list:
+
+### Default Filters Available
+- **All open issues/PRs**
+- **Issues/PRs you created**
+- **Issues/PRs assigned to you**
+- **Issues/PRs where you're @mentioned**
+
+**Steps:**
+1. Go to repository main page
+2. Click **Issues** or **Pull Requests** tab
+3. Click the **Filters** dropdown menu
+4. Select the filter type you want
+
+---
+
+## 2. **Advanced Filter Syntax**
+
+### Basic Search Qualifiers
+
+| Qualifier | Example | Purpose |
+|-----------|---------|---------|
+| `author:` | `author:octocat` | Filter by creator |
+| `assignee:` | `assignee:octocat` | Filter by person assigned |
+| `label:` | `label:"bug"` | Filter by labels |
+| `state:` | `state:open` | Filter by state (open/closed) |
+| `is:` | `is:issue` or `is:pr` | Filter by type |
+| `involves:` | `involves:octocat` | People involved (not just @mentioned) |
+
+### Boolean Operators
+
+**AND operator** (both conditions true):
+```
+label:"question" AND assignee:octocat
+```
+
+**OR operator** (either condition true):
+```
+assignee:octocat OR assignee:hubot
+```
+
+**Negation** (exclude results):
+```
+state:open is:issue -author:octocat
+```
+
+### Nested Filters with Parentheses (up to 5 levels deep)
+```
+(type:"Bug" AND assignee:octocat) OR (type:"Feature" AND assignee:hubot)
+```
+
+---
+
+## 3. **Pull Request-Specific Filters**
+
+### Review Status Filters
+```
+state:open is:pr review:none # Not reviewed yet
+state:open is:pr review:required # Requires review
+state:open is:pr review:approved # Approved
+state:open is:pr review:changes_requested # Changes requested
+state:open is:pr reviewed-by:octocat # Reviewed by someone
+state:open is:pr review-requested:octocat # Awaiting review from someone
+state:open is:pr user-review-requested:@me # Awaiting your review
+state:open is:pr team-review-requested:github/docs # Team review requested
+```
+
+### Draft & Status Filters
+```
+is:draft # Draft PRs
+is:merged # Merged PRs
+is:unmerged # Unmerged PRs
+status:success # All status checks passing
+status:failure # At least one failing check
+status:pending # No status or pending status
+linked:issue # Linked to an issue
+```
+
+---
+
+## 4. **Issue-Specific Filters**
+
+```
+linked:pr # Linked to a PR
+is:closed reason:completed # Closed as completed
+is:closed reason:"not planned" # Closed as not planned
+type:"Bug" # By issue type
+field.priority:high # By issue field values
+has:label # Has any label
+no:project # Missing a project
+```
+
+---
+
+## 5. **Filtering by Labels & Assignees**
+
+### Label Filters
+- **Logical OR** (either label): `label:"bug",\"wip"`
+- **Logical AND** (both labels): `label:"bug" label:"wip"`
+
+### Assignee Filters
+1. Click the **Assignee** dropdown above the list
+2. Select a person or "Assigned to nobody" for unassigned items
+
+---
+
+## 6. **Sorting Options**
+
+Click the **Sort** dropdown to organize by:
+- **Newest** created
+- **Oldest** created
+- **Most** commented
+- **Least** commented
+- **Newest** updated
+- **Oldest** updated
+- **Most** added reactions
+
+---
+
+## 7. **Automation & Sharing Filters**
+
+### Share Your Filtered View
+The URL automatically updates when you apply filters. Example:
+```
+/issues?q=state:open+is:issue+assignee:hubot+sort:created-asc
+```
+
+You can share this URL with anyone to show them the same filtered view.
+
+### GitHub CLI Automation
+
+Use `gh issue list` or `gh pr list` with `--search`:
+
+```bash
+# Issues with no assignee, labeled 'help wanted' or 'bug', sorted by date
+gh issue list --search 'no:assignee label:"help wanted",bug sort:created-asc'
+
+# Pull requests mentioning a team
+gh pr list --search "team:octo-org/octo-team"
+
+# Issues assigned to you
+gh issue list --search 'assignee:@me'
+```
+
+---
+
+## 8. **Pro Tips**
+
+โ **Combine qualifiers**: `state:open is:issue author:octocat label:"bug" assignee:hubot`
+
+โ **Use @copilot**: Works with assignee/author filters: `assignee:@copilot` or `author:@copilot`
+
+โ **Keyboard shortcut**: Focus on search bar with keyboard shortcut (see docs for your OS)
+
+โ **Clear filters**: Click "Clear current search query, filters, and sorts" to reset
+
+---
+
+For the complete reference with all options, see [Filtering and searching issues and pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests) and [Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests).