Skip to content
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

File looses executable bit after editing through web interface #7771

Closed
2 of 7 tasks
jovandeginste opened this issue Aug 6, 2019 · 7 comments · Fixed by #10607
Closed
2 of 7 tasks

File looses executable bit after editing through web interface #7771

jovandeginste opened this issue Aug 6, 2019 · 7 comments · Fixed by #10607
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Milestone

Comments

@jovandeginste
Copy link

Description

When I edit a file through Gitea's web interface, the file's modes are (re)set to 644, effectively losing the executable bit if it was set.

I understand that it's not trivial to change file modes through the web interface (eg. when creating new files), but I believe existing files should keep their modes.

The git log of the above repository:

commit 1635a011929aadf493be0863fb936f56b6ed4188
Author: Jo Vandeginste <Jo.Vandeginste@>
Date:   Tue Aug 6 11:42:38 2019 +0200

    Add an executable script
    
    Signed-off-by: Jo Vandeginste <Jo.Vandeginste@>

diff --git a/script b/script
new file mode 100755
index 0000000..516115d
--- /dev/null
+++ b/script
@@ -0,0 +1 @@
+Some command

commit b7aa45df3b4cb3a085e5b10cae36fbf4c8fed170
Author: jovandeginste <jo.vandeginste@>
Date:   Tue Aug 6 09:44:40 2019 +0000

    'script' updaten

diff --git a/script b/script
old mode 100755
new mode 100644
index 516115d..fa29636
--- a/script
+++ b/script
@@ -1 +1,3 @@
 Some command
+
+some edit
\ No newline at end of file
@stale
Copy link

stale bot commented Oct 5, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Oct 5, 2019
@jovandeginste
Copy link
Author

So... it just won't be fixed then? What a strange procedure!

@stale stale bot removed the issue/stale label Oct 6, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Oct 7, 2019
@dirien
Copy link

dirien commented Jan 8, 2020

hi,

can we get this issue fixed? This is really annoying, especially when you work on scripts for infrastructure.

@ViktorNova
Copy link

+1 I can confirm this bug too
Running Gitea 1.9.5

@jovandeginste
Copy link
Author

Has this been fixed?

@guillep2k
Copy link
Member

@jovandeginste Yes, we've just merged a PR fixing this on the master branch (which will become Gitea 12.0 eventually). See #10607.

@lafriks lafriks modified the milestones: 1.10.5, 1.11.2 Mar 5, 2020
@lafriks
Copy link
Member

lafriks commented Mar 5, 2020

It will be in version 1.11.2

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants