-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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.
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
Bug: Issue and PR are given same counters when using SQLite3 #9249
Comments
Gitea version: 1.10 |
This is by design. |
@guillep2k So it happens on issues and pull requests, despite the type of database? |
Yes. Conceptually, for Gitea a pull request is also an issue, like in GitHub. I believe that there are other systems that don't follow this pattern. |
Right then, closing |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With the latest version of Gitea, let's say there are 0 PRs and 0 issues. We create an issue, and now there is one issue, however when we create a PR, it is labelled as #2, even though there is no first PR.
What I want to say is that the counters are shared across PRs and issues
The text was updated successfully, but these errors were encountered: