Hello, we started to use webhook gitea feature , and we discovered one “strange” behavior. When Path to modified file contains SPACE, then gitea sends incomplete path in commits.modified.
Here is JSON example:
{
“secret”: “”,
“ref”: “refs/heads/master”,
“before”: “aed0bef8b7ef905893e815ebf2a25bceaddc159d”,
“after”: “66069ec2616ce7f00a5722561cf38dd91b47112e”,
“commits”: [
{
“id”: “66069ec2616ce7f00a5722561cf38dd91b47112e”,
“message”: “Gitea Webhook test\n”,
“url”: “https://gitea.local/TEST/Core/commit/66069ec2616ce7f00a5722561cf38dd91b47112e”,
“author”: {
“name”: “msklenicka”,
“email”: “msklenicka@mymail.local”,
“username”: “msklenicka”
},
“committer”: {
“name”: “msklenicka”,
“email”: “msklenicka@mymail.local”,
“username”: “msklenicka”
},
“verification”: null,
“timestamp”: “2021-01-05T10:45:28+01:00”,
“added”: [],
“removed”: [],
“modified”: [
“Java”
]
}
]… }
This is proper filepath: Java Source/jmesa.properties
Gitea version: 1.12.1
Is there any way how to fix this? We cannot change filepaths (We know that it is not good idea have whitecharacters in paths, but its our historical burden)
Thank You very much for help
You mentioned you were on version 1.12.1, are you able to upgrade to the latest stable version 1.13.1 and replicate?
Hi, After update on version 1.13.1, I can confirm same error.
Hi, After update on version 1.13.1, I can confirm same error.
Hello, is there any new information about this issue ?
Hello,
please tell me, do you have any new information about the error I reported above? I need to solve this problem somehow. If you say it’s my problem. It is also a solution. And I’ll know I have to fix it myself.
