Tags from paperdebugger

v2.30.0: docs: add contributing instructions (#127)

2026-02-21T06:14:47Z

docs: add contributing instructions (#127)

## **Benefits**
1. **Clarity**: New contributors understand the workflow immediately
2. **Consistency**: Team follows the same practices
3. **AI-friendly**: Claude, Copilot, and other tools can learn project
conventions
4. **Safety**: Clear rules prevent accidental breaking changes
5. **Flexibility**: Supports both careful testing and fast iteration

---

## Notes
Refer to `CONTRIBUTING.md` for context. I've taken the liberty to make
some assumptions / slight tweaks, explained below:

1. Proposed a simplified branch naming convention, using only prefixes
`feat/*` and `fix/*`, but we enforce semantic classification (e.g. docs,
chore, feat, fix, ci) in PR titles.
[[1]](https://github.com/PaperDebugger/paperdebugger/pull/127/changes#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055R95-R96)
2. Note the standard branching flow (proposed to branch off `staging`
before raising PR to `staging` and subsequently from `staging` to
`main`)
[[2]](https://github.com/PaperDebugger/paperdebugger/pull/127/changes#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055R95-R96)
- Not sure if we should do this over branching off `main`. On one hand,
`main` should always present the latest stable version, but it is also
natural to branch off `staging` since it is the target branch of the
merge after development.
4. Note the merging strategy
[[3]](https://github.com/PaperDebugger/paperdebugger/pull/127/changes#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055R95-R96)

**IMPORTANT NOTE**:
1. It seems `make test` is currently failing for some existing test
cases. To investigate or inform the relevant owners.
2. @Junyi-99 I have disabled `Automatically request Copilot code review`
for PRs to `main` but included it for PRs to `staging` since the new
workflow expects heavy / complex changes to first PR to `staging` before
`main`. To avoid double-review, i disabled this for PRs to `main`. Let
me know if you would like to change or revert this.

---

## **Tasks**

- [x] Create `CONTRIBUTING.md` with branching strategy section
- [x] Configure branch protection rules in GitHub settings
- [x] Set up automated version bumping (if not already configured)
- [x] Document this in README.md or link to CONTRIBUTING.md
- [ ] Announce new policy to team

v2.19.23

2026-02-19T11:51:28Z

v2.29.0

2026-02-18T18:01:47Z

feat: tab completion for citation keys (from `feat/tab-completion`) (#…

…121)

from `feat/tab-completion` to`main`.

Tested on staging. Functionality works as expected. Latency increased
from 2s to 5s, but I suspect it's because the API key was at the brink
of having no credits left. Will look into the latency more.

---------

Co-authored-by: Junyi <[email protected]>
Co-authored-by: 4ndrelim <[email protected]>

v2.28.0: feat: tab completion for citation keys (from `staging`) (#120)

2026-02-18T17:51:28Z

feat: tab completion for citation keys (from `staging`) (#120)

---------

Co-authored-by: Junyi <[email protected]>
Co-authored-by: 4ndrelim <[email protected]>

v2.19.22

2026-02-18T18:02:50Z

v2.19.21

2026-02-18T17:47:57Z

Merge branch 'staging' of https://github.com/PaperDebugger/paperdebugger

into staging

v2.19.20: refactor: update styles and prompt selection logic (#103) (#124)

2026-02-18T17:46:54Z

refactor: update styles and prompt selection logic (#103) (#124)

- Improved accessibility by standardizing `onKeyDown` event handlers to
use consistent formatting for key checks across multiple components.
- Refactored layout of JSX elements for better readability in
`chat.pb.go`, `embed-sidebar`, and various components in the message
entry container.
- General code cleanup to enhance maintainability and readability.

---

> [!NOTE]
> <sup>[Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) is
generating a summary for commit
0a06800. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>

v2.19.19

2026-02-18T17:29:40Z

refactor: improve state management and accessibility in components (#123

)

- Updated `LoadingIndicator` to use `useReducer` for better state
handling.
- Refactored `OnboardingGuide` to utilize `useReducer` for image loading
state.
- Enhanced accessibility by adding `role` and `tabIndex` attributes to
various interactive elements across components.
- Simplified state updates in `ChatHistoryModal` and `LoginWithOverleaf`
by consolidating state management.
- Improved performance in `CodeBlock` by using `useMemo` for highlighted
code.
- General code cleanup and consistency improvements across multiple
components.

v2.19.18

2026-02-17T08:51:18Z

v2.19.17

2026-02-17T07:43:08Z