github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

file_content is not working as expected? #14651

New Issue
Closed
opened 2025-11-02 11:19:01 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 11:19:01 -06:00
Owner
Copy Link

Originally created by @rickyma on GitHub (Jun 25, 2025).

Description

By default this API's response only contains file's metadata. Use comma-separated "includes" options to retrieve more fields. Option "file_content" will try to retrieve the file content, option "lfs_metadata" will try to retrieve LFS metadata.

I am using the new API contents-ext. I pass file_content, but the content of the file is still null?
How could I get the content?

lfs_metadata is working fine.

Gitea Version

latest

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

./gitea web

Database

None

Originally created by @rickyma on GitHub (Jun 25, 2025). ### Description ``` By default this API's response only contains file's metadata. Use comma-separated "includes" options to retrieve more fields. Option "file_content" will try to retrieve the file content, option "lfs_metadata" will try to retrieve LFS metadata. ``` I am using the new API `contents-ext`. I pass file_content, but the content of the file is still `null`? How could I get the content? `lfs_metadata` is working fine. ### Gitea Version latest ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? ./gitea web ### Database None
GiteaMirror added the issue/not-a-bug label 2025-11-02 11:19:01 -06:00
GiteaMirror commented 2025-11-02 11:19:02 -06:00
Author
Owner
Copy Link

@rickyma commented on GitHub (Jun 25, 2025):

@wxiaoguang PTAL

@rickyma commented on GitHub (Jun 25, 2025): @wxiaoguang PTAL
GiteaMirror commented 2025-11-02 11:19:02 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 25, 2025):

// summary: The extended "contents" API, to get file metadata and/or content, or list a directory.

file_content only works for "get file metadata and/or content", but not "list a directory"

@wxiaoguang commented on GitHub (Jun 25, 2025): `// summary: The extended "contents" API, to get file metadata and/or content, or list a directory.` `file_content` only works for "get file metadata and/or content", but not "list a directory"
GiteaMirror commented 2025-11-02 11:19:02 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 25, 2025):

Updated in #34855

	// summary: The extended "contents" API, to get file metadata and/or content, or list a directory.
	// description: It guarantees that only one of the response fields is set if the request succeeds.
	//              Users can pass "includes=file_content" or "includes=lfs_metadata" to retrieve more fields.
	//              "includes=file_content" only works for single file, if you need to retrieve file contents in batch,
	//              use "file-contents" API after listing the directory.
@wxiaoguang commented on GitHub (Jun 25, 2025): Updated in #34855 ``` // summary: The extended "contents" API, to get file metadata and/or content, or list a directory. // description: It guarantees that only one of the response fields is set if the request succeeds. // Users can pass "includes=file_content" or "includes=lfs_metadata" to retrieve more fields. // "includes=file_content" only works for single file, if you need to retrieve file contents in batch, // use "file-contents" API after listing the directory. ```
GiteaMirror commented 2025-11-02 11:19:02 -06:00
Author
Owner
Copy Link

@rickyma commented on GitHub (Jun 25, 2025):

OK, so this is an expected behavior.

@rickyma commented on GitHub (Jun 25, 2025): OK, so this is an expected behavior.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
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#14651
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?