-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Webhooks for issues #132
Labels
type/enhancement
An improvement of existing functionality
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
Milestone
Comments
lunny
added
type/enhancement
An improvement of existing functionality
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
labels
Nov 10, 2016
This was referenced Feb 11, 2017
Closed
resolved by #3929 |
techknowlogick
pushed a commit
that referenced
this issue
Nov 18, 2018
* Add raw blob endpoint This should make it possible to download raw blobs directly from /:repo/:username/raw/blob/:sha1 URLs. * fix: Make it work * As an SHA-ID is no path getRefNameFromPath can't be used to verify file specifying parameter * added relevant change in go-gitea/git #132 Signed-off-by: Berengar W. Lehr <[email protected]> * Update Gopkg.lock Can't update all vendors due to errors Signed-off-by: Berengar W. Lehr <[email protected]> * style: Add Gitea copyright header * feat: Added integration test for /repo/u/r/raw/blob * fix: correct year in copyright header
lunny
pushed a commit
to lunny/gitea
that referenced
this issue
Feb 7, 2019
* Add repo_blob This adds a new Repository.GetBlob(id) method for use by gitea. * This is a follow-up for PR go-gitea#121 to implement blob_api including full test coverage Signed-off-by: Berengar W. Lehr <[email protected]>
6543
pushed a commit
to 6543-forks/gitea
that referenced
this issue
Feb 26, 2024
When searching for repository topics, either via the API, or via Explore, paging did not work correctly, because it only applied when the `page` parameter was non-zero. Paging should have applied when the page size is greater than zero, which is what this patch does. As a result, both the API, and the Explore endpoint will return paged results (30 by default). As such, when managing topics on the frontend, the offered completions will also be limited to a pageful of results, based on what the user has already typed. This drastically reduces the amount of traffic, and also the number of the topics to choose from, and thus, the rendering time too. The topics will be returned by popularity, with most used topics first. A single page will contain `[api].DEFAULT_PAGING_NUM` (30 by default) items that match the query. That's plenty to choose from. Fixes go-gitea#132. Signed-off-by: Gergely Nagy <[email protected]> (cherry picked from commit 64d4ff41dbab7b3b84571b595158c3b451f53af7) (cherry picked from commit 06b808fa2c0ddd52ca4569157892a0c7fc154b1f) (cherry picked from commit 9205c9266a7d2b058100d03f5f3272f670f35866) (cherry picked from commit 47863d4f724e7d2465acd6fca91e98157c60a29b)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
type/enhancement
An improvement of existing functionality
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
I will just add this here, from Gogs issues. Title is self explanatory, I think this is must have feature.
#2319
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39116501-webhooks-for-issues?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: