github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 20:07:40 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[PR #5062] [CLOSED] only chown directories during docker setup if necessary. Fix #4425 #17620

New Issue
Closed
opened 2025-11-02 14:31:12 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 14:31:12 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/5062
Author: @fabian-braun
Created: 10/10/2018
Status: ❌ Closed

Base: release/v1.5 ← Head: release/v1.5

📝 Commits (1)

  • 7ebfd06 only chown directories during docker setup if necessary. Fix #4425

📊 Changes

1 file changed (+4 additions, -1 deletions)

View changed files

📝 docker/etc/s6/gitea/setup (+4 -1)

📄 Description

This PR fixes issue #4425 .
Instead of blindly running chown during setup, we check that the directory is not already owned by the correct user. Currently the check is non-recursive for speed (only checks the ownership of top-level directory).

🔄 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/go-gitea/gitea/pull/5062 **Author:** [@fabian-braun](https://github.com/fabian-braun) **Created:** 10/10/2018 **Status:** ❌ Closed **Base:** `release/v1.5` ← **Head:** `release/v1.5` --- ### 📝 Commits (1) - [`7ebfd06`](https://github.com/go-gitea/gitea/commit/7ebfd06dbee553c6f3e0a956b3ad4a9d621a5d53) only chown directories during docker setup if necessary. Fix #4425 ### 📊 Changes **1 file changed** (+4 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docker/etc/s6/gitea/setup` (+4 -1) </details> ### 📄 Description This PR fixes issue #4425 . Instead of blindly running `chown` during setup, we check that the directory is not already owned by the correct user. Currently the check is non-recursive for speed (only checks the ownership of top-level directory). --- <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 2025-11-02 14:31:12 -06:00
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 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#17620
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?