Skip to content

Commit e7d61db

Browse files
miparnisarimiparnisari
committed
Merge remote-tracking branch 'origin/master' into fix-readme
2 parents a5f07e9 + a887eba commit e7d61db

63 files changed

Lines changed: 7055 additions & 7051 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.claude/skills/github-issues/SKILL.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
name: github-issues
3+
description: Manage GitHub issues using the `gh` CLI. Use when the user asks to list, view, create, edit, close, reopen, comment on, or search GitHub issues.
4+
tools: Bash
5+
---
6+
7+
# GitHub Issues Skill
8+
9+
This project's repository is `benchmark-action/github-action-benchmark`. Always use `-R benchmark-action/github-action-benchmark` unless the user explicitly specifies a different repo.
10+
11+
## Common Operations
12+
13+
### List issues
14+
```bash
15+
gh issue list -R benchmark-action/github-action-benchmark
16+
gh issue list -R benchmark-action/github-action-benchmark --state all
17+
gh issue list -R benchmark-action/github-action-benchmark --state closed
18+
gh issue list -R benchmark-action/github-action-benchmark --label "bug"
19+
gh issue list -R benchmark-action/github-action-benchmark --assignee "@me"
20+
gh issue list -R benchmark-action/github-action-benchmark --author monalisa
21+
gh issue list -R benchmark-action/github-action-benchmark --search "error no:assignee"
22+
gh issue list -R benchmark-action/github-action-benchmark --limit 100
23+
gh issue list -R benchmark-action/github-action-benchmark --json number,title,state,labels,url
24+
```
25+
26+
### View an issue
27+
```bash
28+
gh issue view 123 -R benchmark-action/github-action-benchmark
29+
gh issue view 123 -R benchmark-action/github-action-benchmark --comments
30+
gh issue view 123 -R benchmark-action/github-action-benchmark --json title,body,comments,labels,assignees,state,url
31+
```
32+
33+
### Create an issue
34+
```bash
35+
gh issue create -R benchmark-action/github-action-benchmark --title "Title" --body "Body"
36+
gh issue create -R benchmark-action/github-action-benchmark --title "Bug" --label "bug" --assignee "@me"
37+
gh issue create -R benchmark-action/github-action-benchmark --web
38+
```
39+
40+
### Edit an issue
41+
```bash
42+
gh issue edit 123 -R benchmark-action/github-action-benchmark --title "New title"
43+
gh issue edit 123 -R benchmark-action/github-action-benchmark --body "Updated body"
44+
gh issue edit 123 -R benchmark-action/github-action-benchmark --add-label "priority:high" --remove-label "triage"
45+
gh issue edit 123 -R benchmark-action/github-action-benchmark --add-assignee "@me"
46+
```
47+
48+
### Close / Reopen
49+
```bash
50+
gh issue close 123 -R benchmark-action/github-action-benchmark
51+
gh issue close 123 -R benchmark-action/github-action-benchmark --reason "not planned"
52+
gh issue reopen 123 -R benchmark-action/github-action-benchmark
53+
```
54+
55+
### Comment on an issue
56+
```bash
57+
gh issue comment 123 -R benchmark-action/github-action-benchmark --body "My comment"
58+
```
59+
60+
### Pin / Unpin
61+
```bash
62+
gh issue pin 123 -R benchmark-action/github-action-benchmark
63+
gh issue unpin 123 -R benchmark-action/github-action-benchmark
64+
```
65+
66+
## Workflow
67+
68+
1. **Determine the intent** from the user's request (list, view, create, edit, close, comment, etc.)
69+
2. **Always pass** `-R benchmark-action/github-action-benchmark` unless the user says otherwise
70+
3. **Run the appropriate `gh issue` command** using the Bash tool
71+
4. **Present the output** clearly; for `--json` output, summarize the relevant fields rather than dumping raw JSON
72+
73+
## Tips
74+
75+
- Issue numbers and URLs are both valid arguments
76+
- Use `--json fields` + `--jq expression` for precise filtering
77+
- `gh issue status -R benchmark-action/github-action-benchmark` shows issues relevant to you

‎.codecov.yml‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
comment: off
2-
31
coverage:
42
status:
53
project: yes

‎.coderabbit.yaml‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
reviews:
2+
pre_merge_checks:
3+
docstrings:
4+
mode: "off"

‎.github/workflows/catch2.yml‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ permissions:
1010

1111
jobs:
1212
benchmark:
13-
name: Run C++ benchmark example
14-
runs-on: ubuntu-20.04
13+
name: Run Catch2 C++ Benchmark Framework example (v3.x)
14+
runs-on: ubuntu-latest
1515
steps:
1616
- uses: actions/checkout@v4
1717
- name: Build and run benchmarks with Catch2
@@ -25,7 +25,7 @@ jobs:
2525
- name: Store benchmark result
2626
uses: benchmark-action/github-action-benchmark@v1
2727
with:
28-
name: Catch2 Benchmark
28+
name: Catch2 Benchmark (v3)
2929
tool: 'catch2'
3030
output-file-path: examples/catch2/benchmark_result.txt
3131
github-token: ${{ secrets.GITHUB_TOKEN }}
@@ -34,12 +34,12 @@ jobs:
3434
alert-threshold: '200%'
3535
comment-on-alert: true
3636
fail-on-alert: true
37-
alert-comment-cc-users: '@bernedom,@ktrz'
37+
alert-comment-cc-users: '@ktrz'
3838

3939
- name: Store benchmark result - separate results repo
4040
uses: benchmark-action/github-action-benchmark@v1
4141
with:
42-
name: Catch2 Benchmark
42+
name: Catch2 Benchmark (v3)
4343
tool: 'catch2'
4444
output-file-path: examples/catch2/benchmark_result.txt
4545
github-token: ${{ secrets.BENCHMARK_ACTION_BOT_TOKEN }}
@@ -48,5 +48,5 @@ jobs:
4848
alert-threshold: '200%'
4949
comment-on-alert: true
5050
fail-on-alert: true
51-
alert-comment-cc-users: '@bernedom,@ktrz'
51+
alert-comment-cc-users: '@ktrz'
5252
gh-repository: 'github.com/benchmark-action/github-action-benchmark-results'

‎.github/workflows/catch2_v2.yml‎

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
name: Catch2 C++ Example
2+
on:
3+
push:
4+
branches:
5+
- master
6+
7+
permissions:
8+
contents: write
9+
deployments: write
10+
11+
jobs:
12+
benchmark:
13+
name: Run Catch2 C++ Benchmark Framework example (v2.x)
14+
runs-on: ubuntu-latest
15+
steps:
16+
- uses: actions/checkout@v4
17+
- name: Build and run benchmarks with Catch2
18+
run: |
19+
cd examples/catch2_v2
20+
mkdir build && cd build
21+
cmake -DCMAKE_BUILD_TYPE=Release ..
22+
cmake --build . --config Release
23+
./Catch2_bench | tee ../benchmark_result.txt
24+
25+
- name: Store benchmark result
26+
uses: benchmark-action/github-action-benchmark@v1
27+
with:
28+
name: Catch2 Benchmark
29+
tool: 'catch2'
30+
output-file-path: examples/catch2_v2/benchmark_result.txt
31+
github-token: ${{ secrets.GITHUB_TOKEN }}
32+
auto-push: true
33+
# Show alert with commit comment on detecting possible performance regression
34+
alert-threshold: '200%'
35+
comment-on-alert: true
36+
fail-on-alert: true
37+
alert-comment-cc-users: '@ktrz'
38+
39+
- name: Store benchmark result - separate results repo
40+
uses: benchmark-action/github-action-benchmark@v1
41+
with:
42+
name: Catch2 Benchmark
43+
tool: 'catch2'
44+
output-file-path: examples/catch2_v2/benchmark_result.txt
45+
github-token: ${{ secrets.BENCHMARK_ACTION_BOT_TOKEN }}
46+
auto-push: true
47+
# Show alert with commit comment on detecting possible performance regression
48+
alert-threshold: '200%'
49+
comment-on-alert: true
50+
fail-on-alert: true
51+
alert-comment-cc-users: '@ktrz'
52+
gh-repository: 'github.com/benchmark-action/github-action-benchmark-results'

0 commit comments

Comments
 (0)