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

don't rebuild from scratch each time #5

Open
lalitkapoor opened this issue Feb 22, 2014 · 2 comments
Open

don't rebuild from scratch each time #5

lalitkapoor opened this issue Feb 22, 2014 · 2 comments
Assignees

Comments

@lalitkapoor
Copy link
Owner

We should set the since option where possible to update the changelog. This will save on api calls and reduce time to generate the file.

Consider storing the since values directly in the markdown file as a comment or in another file. Read these values before building changelog.

Add a --rebuild flag to rebuild changelog from scratch (ignore since)

References:

Conditional requests

Most responses return an ETag header. Many responses also return a Last-Modified header. You can use the values of these headers to make subsequent requests to those resources using the If-None-Match and If-Modified-Since headers, respectively. If the resource has not changed, the server will return a 304 Not Modified. Also note: making a conditional request and receiving a 304 response does not count against your Rate Limit, so we encourage you to use it whenever possible.

http://developer.github.com/v3/#conditional-requests

@nunofgs
Copy link

nunofgs commented Oct 31, 2014

Yes. Please add this 👍

@tunnckoCore
Copy link

Or just try to read and parse (meaning, get a latest version) local CHANGELOG file.

But yea, in long term maybe this would be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants