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.

Sign up for GitHub

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

Jump to bottom

Broken cache invalidation #40

Open
djds23 opened this issue Jan 20, 2016 · 0 comments
Open

Broken cache invalidation #40

djds23 opened this issue Jan 20, 2016 · 0 comments

Comments

@djds23
Copy link
Owner

djds23 commented Jan 20, 2016

  • github stops reporting the number of commits after 250, this breaks the current approach
  • the commit number does not update after a rebase, this breaks the current approach
@djds23 djds23 changed the title github stops reporting the number of commits after 250, this will break cache invalidation github stops reporting the number of commits after 250, breaks cache invalidation Jan 20, 2016
@djds23 djds23 changed the title github stops reporting the number of commits after 250, breaks cache invalidation Broken cache invalidation Jan 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@djds23