-
-
Notifications
You must be signed in to change notification settings - Fork 383
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
Environment Variable CI_COMMIT_AUTHOR_EMAIL is wrong #2971
Comments
I have further investigated the issue and I can see that in the web hook gitea sends something strange. For the Example of the payload:
|
IIRC:
More context: go-gitea/gitea#28532 |
For Woodpecker wouldn't it make more sense to set environment variables like CI_COMMIT_AUTHOR_... to the author of the commit, not the user who did the push? |
This is also happening to me. Is there some updates on this or reasons why the CI_COMMIT_AUTHOR_... variables should not contain the actual commiter's data? |
Likely a bug on the first look. Contributions welcome. |
i'm seeing this with a mirrored repo (gitlab pushing to forgejo) where the data is set according to the user used by gitlab to authenticate against forgejo (a bot account on forgejo i've created for this purpose) rather than the expected data of the committer. |
Component
server, agent
Describe the bug
I am running Gitea with Woodpecker CI. I have noticed that for some time now, the built in
CI_COMMIT_AUTHOR_EMAIL
environment variable is wrong. I have setup a sample project, with nothing more than a simple pipeline.Here is the git log from the CLI:
Here is the woodpecker.yml
Here is the output after running the pipeline:
System Info
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: