github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Pushes via deployment write keys do not trigger reindex #1697

New Issue
Closed
opened 2025-11-02 04:10:01 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2025-11-02 04:10:01 -06:00
Owner
Copy Link

Originally created by @mqudsi on GitHub (Apr 14, 2018).

Description

It seems pushes to repos with rw deployment keys do not trigger a reindex of the repo or the "commit" event.

  1. Create repo
  2. Add deployment key with write access
  3. Push to repo with deployment key
  4. webui does not reflect changes, repo continues to show as if new

Reproduced on try.gitea: https://try.gitea.io/mqudsi/test-deploy
That repo appears blank, but it has content.

Originally created by @mqudsi on GitHub (Apr 14, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): `38a9cda` - Git version: n/a - Operating system: n/a - Database (use `[x]`): n/a - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [X] Yes: https://try.gitea.io/mqudsi/test-deploy - [ ] No - [ ] Not relevant - Log gist: ## Description It seems pushes to repos with rw deployment keys do not trigger a reindex of the repo or the "commit" event. 1. Create repo 2. Add deployment key with write access 3. Push to repo with deployment key 4. webui does not reflect changes, repo continues to show as if new Reproduced on try.gitea: https://try.gitea.io/mqudsi/test-deploy That repo *appears* blank, but it has content.
GiteaMirror added the type/bug label 2025-11-02 04:10:01 -06:00
GiteaMirror commented 2025-11-02 04:10:01 -06:00
Author
Owner
Copy Link

@bjoe2k4 commented on GitHub (Sep 15, 2018):

This bug just hit me hard and took me hours to realize what the problem was. Any update on this?

@bjoe2k4 commented on GitHub (Sep 15, 2018): This bug just hit me hard and took me hours to realize what the problem was. Any update on this?
GiteaMirror commented 2025-11-02 04:10:01 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 9, 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[bot] commented on GitHub (Jan 9, 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.
GiteaMirror commented 2025-11-02 04:10:01 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 9, 2019):

@bjoe2k4 need more investigation.

@lunny commented on GitHub (Jan 9, 2019): @bjoe2k4 need more investigation.
GiteaMirror commented 2025-11-02 04:10:02 -06:00
Author
Owner
Copy Link

@dakira commented on GitHub (Jan 31, 2019):

I'm using the latest HEAD and have the exact same problem. Using read/write deploy keys, the cache is not invalidated when pushing, using a user key, it is. Can I help investigating @lunny?

@dakira commented on GitHub (Jan 31, 2019): I'm using the latest HEAD and have the exact same problem. Using read/write deploy keys, the cache is not invalidated when pushing, using a user key, it is. Can I help investigating @lunny?
GiteaMirror commented 2025-11-02 04:10:02 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 31, 2019):

This is pushing with SSH keys?

I bet the environment variables for the hooks aren't being set properly.

@zeripath commented on GitHub (Jan 31, 2019): This is pushing with SSH keys? I bet the environment variables for the hooks aren't being set properly.
GiteaMirror commented 2025-11-02 04:10:02 -06:00
Author
Owner
Copy Link

@mqudsi commented on GitHub (Feb 1, 2019):

Not regular ssh key push, pushing with rw-enabled deployment keys.

@mqudsi commented on GitHub (Feb 1, 2019): Not regular ssh key push, pushing with rw-enabled deployment keys.
GiteaMirror commented 2025-11-02 04:10:02 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 2, 2019):

Yep, taking a look at gitea cmd/serv.go the environment settings aren't properly set.

@zeripath commented on GitHub (Feb 2, 2019): Yep, taking a look at gitea cmd/serv.go the environment settings aren't properly set.
GiteaMirror commented 2025-11-02 04:10:03 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 2, 2019):

I've pushed a branch to github but not opened a PR just yet until I've had a chance to test it

@zeripath commented on GitHub (Feb 2, 2019): I've pushed a branch to github but not opened a PR just yet until I've had a chance to test it
GiteaMirror commented 2025-11-02 04:10:03 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 3, 2019):

@mqudsi maybe you can confirm that #5935 fix this issue.

@lunny commented on GitHub (Feb 3, 2019): @mqudsi maybe you can confirm that #5935 fix this issue.
GiteaMirror commented 2025-11-02 04:10:03 -06:00
Author
Owner
Copy Link

@dakira commented on GitHub (Feb 5, 2019):

@lunny I can confirm this fixes the issue.

@dakira commented on GitHub (Feb 5, 2019): @lunny I can confirm this fixes the issue.
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 type/bug
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#1697
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?