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

Fix failing to cache last commit with key being to long (#12151) #12161

Conversation

lafriks
Copy link
Member

@lafriks lafriks commented Jul 6, 2020

Backport #12151

@lafriks lafriks added this to the 1.12.2 milestone Jul 6, 2020
@lafriks lafriks changed the title Use hash of repo path, ref and entrypath as cache key (#12151) Fix failing to cache last commit with key being to long (#12151) Jul 6, 2020
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jul 6, 2020
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Jul 6, 2020
@lunny lunny merged commit 3daedb3 into go-gitea:release/v1.12 Jul 6, 2020
@lafriks lafriks deleted the backport/fix/last_cache_cachekey_length branch July 6, 2020 08:53
@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
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants