Skip to content

Issues: GiteaBot/gitea-backporter

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10 Open 30 Closed
10 Open 30 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Idea: Labels to indicate whether automated backport is possible
#132 opened Jul 13, 2024 by silverwind
Add a renminder to send a PR to https://gitea.com/gitea/docs when a PR's app.example.ini changed.
#131 opened Jul 11, 2024 by lunny
3
lgtm/blocked not being removed on review re-request
#121 opened Feb 23, 2024 by silverwind
4
Incorrect milestone
#112 opened Dec 11, 2023 by yp05327
1
Fails to backport clean cherry-picks
#110 opened Oct 8, 2023 by silverwind
15
Detected merge conflict wrong. bug Something isn't working
#109 opened Oct 2, 2023 by lunny
2
Do a frontport PR when a merged PR has labeled frontend/main enhancement New feature or request
#107 opened Sep 8, 2023 by lunny
4
Bug: wrong manual backport message (not always)
#94 opened Jul 7, 2023 by wolfogre
5
Idea: Run a command on a PR branch
#88 opened May 29, 2023 by silverwind
6
Delete merged branches
#11 opened Mar 10, 2023 by yardenshoham
ProTip! Add no:assignee to see everything that’s not assigned.