github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-07 12:37:43 -05:00
Code Issues 103 Packages Projects Releases 93 Wiki Activity

[PR #182] [MERGED] Fix issue 168: repo descriptions and toast overlap #1820

New Issue
Closed
opened 2026-04-27 19:11:08 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-27 19:11:08 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/182
Author: @arunavo4
Created: 2/24/2026
Status: ✅ Merged
Merged: 2/24/2026
Merged by: @arunavo4

Base: main ← Head: codex/issue-168-interval-description-toast

📝 Commits (2)

  • 6829bcf Fix issue 168 description and toast placement
  • 5eb1608 Move app toasts to top center

📊 Changes

3 files changed (+14 additions, -2 deletions)

View changed files

📝 README.md (+12 -0)
📝 src/components/layout/MainLayout.tsx (+1 -1)
📝 src/lib/gitea.ts (+1 -1)

📄 Description

Summary

  • mirror repository descriptions into Gitea instead of sending an empty description
  • move app toasts to top-right so they do not block the floating "Add Repository" button
  • document mirror interval behavior with Gitea/Forgejo MIN_INTERVAL in README troubleshooting

Why

Issue #168 reported three problems:

  1. interval confusion with Forgejo/Gitea minimum interval settings
  2. mirrored repositories missing descriptions
  3. toast notifications blocking the add button on repository pages

This PR fixes #2 and #3 in code and addresses #1 with clear operational documentation.

Validation

  • bun test src/lib/gitea.test.ts src/lib/gitea-enhanced.test.ts src/lib/mirror-sync-fix.test.ts

Fixes #168

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/RayLabsHQ/gitea-mirror/pull/182 **Author:** [@arunavo4](https://github.com/arunavo4) **Created:** 2/24/2026 **Status:** ✅ Merged **Merged:** 2/24/2026 **Merged by:** [@arunavo4](https://github.com/arunavo4) **Base:** `main` ← **Head:** `codex/issue-168-interval-description-toast` --- ### 📝 Commits (2) - [`6829bcf`](https://github.com/RayLabsHQ/gitea-mirror/commit/6829bcff9132ef0cbfbd4931eccd1f1bc5d583e3) Fix issue 168 description and toast placement - [`5eb1608`](https://github.com/RayLabsHQ/gitea-mirror/commit/5eb160861d80613a46fc99803cbe08e40df3179b) Move app toasts to top center ### 📊 Changes **3 files changed** (+14 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+12 -0) 📝 `src/components/layout/MainLayout.tsx` (+1 -1) 📝 `src/lib/gitea.ts` (+1 -1) </details> ### 📄 Description ## Summary - mirror repository descriptions into Gitea instead of sending an empty description - move app toasts to top-right so they do not block the floating "Add Repository" button - document mirror interval behavior with Gitea/Forgejo `MIN_INTERVAL` in README troubleshooting ## Why Issue #168 reported three problems: 1. interval confusion with Forgejo/Gitea minimum interval settings 2. mirrored repositories missing descriptions 3. toast notifications blocking the add button on repository pages This PR fixes #2 and #3 in code and addresses #1 with clear operational documentation. ## Validation - `bun test src/lib/gitea.test.ts src/lib/gitea-enhanced.test.ts src/lib/mirror-sync-fix.test.ts` Fixes #168 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-27 19:11:08 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#1820
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?