Jiseoup/showmycodePublic
EN|KO
  • 코드
  • 커밋
  • 풀 리퀘스트

풀 리퀘스트페이지 5

  • Jiseoup
    Merged

    feat: add pagination and detail pages for commits and PRs

    #5

    feat/pagination-and-detail-pages → main

    ## Related Issue N/A ## Changes - Add page-based pagination to commit history (50/page) and PR list (30/page) - Add PR detail page with Overview (Markdown rendered), Commits, and Files changed tabs - Add commit detail page with file diff view - Add `FilesChanged` client component with per-file and global fold/unfold toggle - Add `MarkdownBody` component using `react-markdown` + `remark-gfm` - Add GitHub API helpers: `getCommit`, `getPull`, `getPullFiles`, `getPullCommits` - Update i18n strings (ko/en) for all new UI text ## How to Verify 1. Navigate to the Commits tab — verify prev/next pagination buttons appear correctly 2. Click a commit — verify detail page shows commit message and colored diff 3. Navigate to the PR list — verify pagination works 4. Click a PR — verify Overview tab renders Markdown (headings, lists, code blocks, tables, task lists) 5. Click Commits tab in PR detail — verify list appears and each item links to commit detail 6. Click Files changed tab — verify diff is shown with `+` green / `-` red coloring 7. On Files changed, test fold/unfold per file and global toggle button 8. Switch locale (ko/en) — verify all new strings display correctly 9. Toggle dark mode — verify all new pages render correctly ## Checklist - [x] `npm run build` passes - [x] `npm run lint` passes - [x] New/updated strings added to both `locales/ko.json` and `locales/en.json` (if applicable)

    Jiseoup · 2026년 4월 3일feat
  • Jiseoup
    Merged

    fix: await async params in GitHub API route for Next.js 16

    #4

    fix/api-route-params → main

    ## Related Issue N/A — CI build failure ## Changes - Update `params` type from `{ path: string[] }` to `Promise<{ path: string[] }>` in API route - Add `await params` to match Next.js 16 async params convention ## How to Verify 1. `npx tsc --noEmit` passes with no errors 2. `npm run build` passes (Node >= 20) 3. Access `/api/github/repos/{owner}/{repo}` and confirm it still proxies correctly ## Checklist - [x] `npm run build` passes - [x] `npm run lint` passes - [ ] New/updated strings added to both `dictionaries/ko.json` and `dictionaries/en.json` (if applicable) - [ ] Tests added for new functionality (if applicable)

    Jiseoup · 2026년 3월 31일fix
  • Jiseoup
    Merged

    docs: add i18n branch and commit convention to project guidelines

    #3

    docs/add-i18n-convention → main

    ## Related Issue N/A ## Changes - Add `i18n/` prefix to branch naming convention in CLAUDE.md and CONTRIBUTING.md - Add `i18n:` to commit message convention in CLAUDE.md and CONTRIBUTING.md - Add `i18n:` commit message example in CONTRIBUTING.md ## How to Verify 1. Review CLAUDE.md — branch strategy and commit messages sections 2. Review CONTRIBUTING.md — branch naming table and commit examples ## Checklist - [x] `npm run build` passes - [x] `npm run lint` passes - [ ] New/updated strings added to both `dictionaries/ko.json` and `dictionaries/en.json` (if applicable) - [ ] Tests added for new functionality (if applicable)

    Jiseoup · 2026년 3월 31일docs
  • Jiseoup
    Merged

    feat: display repository topics on home page

    #2

    feat/repo-topics → main

    ## Related Issue N/A ## Changes - Add `topics` field to `GhRepo` type in `lib/github.ts` - Display topic tags as blue pills below repo description in `RepoCard.tsx` - Hidden when repository has no topics ## How to Verify 1. Set up `.env.local` with a repo that has GitHub topics configured 2. `npm run dev` and open the home page 3. Confirm topic tags appear below the repository description ## Checklist - [x] `npm run build` passes - [x] `npm run lint` passes - [ ] New/updated strings added to both `dictionaries/ko.json` and `dictionaries/en.json` (if applicable) - [ ] Tests added for new functionality (if applicable)

    Jiseoup · 2026년 3월 31일feat
  • Jiseoup
    Merged

    chore: add CI workflow and GitHub issue/PR templates

    #1

    chore/ci-templates → main

    ## Related Issue N/A — initial open-source infrastructure setup ## Changes - Add GitHub Actions CI workflow (Node 20/22, lint + build) - Add PR template - Add Issue templates (bug report, feature request) ## How to Verify 1. Check `.github/workflows/ci.yml` triggers on push/PR to `main` 2. Open a new Issue and confirm templates appear 3. Open a new PR and confirm template is pre-filled ## Checklist - [x] `npm run build` passes - [x] `npm run lint` passes - [ ] New/updated strings added to both `dictionaries/ko.json` and `dictionaries/en.json` (if applicable) - [ ] Tests added for new functionality (if applicable)

    Jiseoup · 2026년 3월 31일chore
← 이전페이지 5