You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.**Fetch the issue**: Use `gh issue view $ARGUMENTS` to read the issue details from the GitHub repository. Understand what the bug or feature request is about.
6
+
7
+
2.**Create a branch**: Create and checkout a new branch named `fix-$ARGUMENTS` from main:
8
+
```
9
+
git checkout -b fix-$ARGUMENTS
10
+
```
11
+
12
+
3.**Write a failing test**: Based on the issue description, write a test that reproduces the problem. The test should fail initially, demonstrating the bug exists.
13
+
14
+
4.**Run the test**: Execute the failing test to confirm it fails as expected. If the test requires a database and fails due to connection issues, that's acceptable - focus on the test logic being correct.
15
+
16
+
5.**Diagnose the issue**: Analyze the codebase to understand why the bug occurs. Look at the relevant source files and trace through the logic.
17
+
18
+
6.**Implement the fix**: Make the necessary code changes to fix the issue. Keep changes minimal and focused.
19
+
20
+
7.**Verify the fix**: Run the test again to confirm it now passes (or would pass with a database connection).
21
+
22
+
8.**Commit and push**: Stage all changes, commit with a descriptive message referencing the issue number, and push the branch:
- Add default `ORDER BY` primary key when no order is specified to ensure deterministic pagination results ([#73](https://github.com/aarondfrancis/fast-paginate/issues/73))
4
+
- Add `$total` parameter to `fastPaginate()` to allow skipping the COUNT query ([#74](https://github.com/aarondfrancis/fast-paginate/issues/74))
0 commit comments