You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Gitea API to create or update a file and commit it, the "Author" is committed as "Commit" and vice versa.
From the log gist is obvious that not only the git repo is indicating the wrong person, but also the SQL insert is wrong. Presumably the root cause is within the API itself.
lukas@dev:~$ git clone https://try.gitea.io/sand-giteabug1/giteabug1-repro.git
[...]
lukas@dev:~$ cd giteabug1-repro/
lukas@dev:~/giteabug1-repro$
lukas@dev:~/giteabug1-repro$ git show --pretty=fuller
commit 011459fc45499859f1deacd02a506fdc08961a24
Author: CommitterName <commit@example.com>
AuthorDate: Sun Dec 8 19:40:16 2019 +0000
Commit: AuthorName <author@example.com>
CommitDate: Sun Dec 8 19:40:16 2019 +0000
Create a new file
diff --git a/aNewFile b/aNewFile
new file mode 100644
index 0000000..793aa68
--- /dev/null
+++ b/aNewFile
@@ -0,0 +1 @@
+This is a test
\ No newline at end of file
lukas@dev:~/giteabug1-repro$
Screenshots
The text was updated successfully, but these errors were encountered:
1.10.1
release ortry.gitea.io
repro with1.11.0+dev-393-g95a57394a
2.17.1
or whatevertry.gitea.io
runstry.gitea.io
runs[x]
):Description
When using Gitea API to create or update a file and commit it, the "Author" is committed as "Commit" and vice versa.
From the log gist is obvious that not only the git repo is indicating the wrong person, but also the SQL insert is wrong. Presumably the root cause is within the API itself.
Test repository on try.gitea.io:
https://try.gitea.io/sand-giteabug1/giteabug1-repro
Request to commit a new file:
https://try.gitea.io/sand-giteabug1/giteabug1-repro/commit/011459fc45499859f1deacd02a506fdc08961a24
Screenshots
The text was updated successfully, but these errors were encountered: